vvivekiyer opened a new issue, #9061: URL: https://github.com/apache/pinot/issues/9061
Currently, a raw column (where forward index stores raw values) cannot support an inverted index. A raw column is typically used for high cardinality metric columns where dictionary is not very helpful. 1. Neither does it help saving forward index storage space 2. Nor does it help with filter performance In fact, queries that use such column without dictionary in other parts that require reading the actual values - selection / projection / order by / transform / aggregate can get perf benefit by avoiding double lookup. However, the column automatically looses out on inverted index or sorted index since they are dictionary based. So if there is a usecase where a raw column is also extensively used in filters, performance can be bad due to lack of inverted index. So, creating this issue to evaluate if building inverted index for a raw column is beneficial. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
