egalpin opened a new issue, #11464: URL: https://github.com/apache/pinot/issues/11464
For cases where `range` index is used for timestamps, I have observed that using a complimentary inverted index at great time granularity greatly improves performance. Ex. if I have epochMs values in a field, and I convert those to yyyy-MM-dd (2023-08-30) strings which are stored in a separate column with inverted index enabled, this massively improves query performance since the inverted index can efficiently produce the superset of docs that could match the epochMs range. In my case, I pad the range with an additional day on each side to allow for ignoring timezone conversions. This might be nice to provide out of the box as a "special" range index where all of this is handled under-the-hood, at user configurable granularity (hour instead of day, for example). Might not be worth the trouble either, as it's definitely doable as-is be self-managing. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
