[GitHub] [incubator-pinot] Jackie-Jiang commented on issue #6626: [Query Optimizer Improvement] IN statement for timestamp applied as pruning mechanism properly

[GitBox <gi...@apache.org>]

Jackie-Jiang commented on issue #6626:
URL: https://github.com/apache/incubator-pinot/issues/6626#issuecomment-788553474


   @dongxiaoman Do you have inverted index on `created_at` column? If not, then this is expected because in order to solve the `IN` clause, we have to create a set and match each value with the set. While for the range filter, we just need to compare the value with the range which is faster than set lookup.
   @kishoreg We cannot really use min-max from the `IN` clause unless the values are sequential. E.g. `IN (1, 2, 4)` is not equivalent to `BETWEEN 1 AND 4` because `3` does not match the `IN` clause


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org