[GitHub] [pinot] shwin commented on issue #10986: Count discrepancy among `in`/`=` and `<` queries using timestamp index

[via GitHub]

shwin commented on issue #10986:
URL: https://github.com/apache/pinot/issues/10986#issuecomment-1613790055

   is there a way I can disable segment pruning or something similar so we can 
figure that out?
   
   ie, if there is a way to query a single segment and _not_ do segment pruning 
that might be useful; I did try including the segmentName in the where clause 
of the query but not sure if that helps.
   
   And for what it's worth, when trying it again, for the `=` query I get:
   
![image](https://github.com/apache/pinot/assets/1700973/bba50ad7-eb0e-4b7c-a0c5-79abe6b34d01)
   
   That is, `PLAN_START(numSegmentsForThisPlan:1)`.
   
   When I run the query on my current table, I get _3_ segments back, so not 
sure what that number means.
   
   I get the same line for the `>= + <` query:
   
   
![image](https://github.com/apache/pinot/assets/1700973/6c9ec555-78d7-42aa-ab5c-271e3372243a)
   
   When I run the query on my current table, I get _4_ segments back.
   
   So imo not sure if that explain line is super useful here? But y'all would 
know better than me!


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

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