numEntriesScannedInFilter > numDocsScanned in certain scenarios
See original GitHub issueWhen running a query like the following
SELECT COUNT(*) FROM table WHERE id = x AND time BETWEEN a AND b
numEntriesScannedInFilter
is showing more records than the ones scanned numDocsScanned
, why is this the case? shouldn’t it only scan the number that we have selected already on?
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
[GitHub] [pinot] lfernandez93 commented on issue #7642
[GitHub] [pinot] lfernandez93 commented on issue #7642: numEntriesScannedInFilter > numDocsScanned in certain scenarios.
Read more >Troubleshooting Pinot - Apache Pinot Docs
Specifically look at numEntriesScannedInFilter and numDocsScanned . ... If numDocsScanned is very high, that means the selectivity for the query is low and ......
Read more >Low Latency (OLAP) Movie Rating Analytics Using Apache Pinot
Use Apache Pinot to stream ingesting movie rating events across countries from a Kafka topic and make them available for immediate querying ...
Read more >Apache Pinot: Exploring range queries - Mark Needham
We loaded this data into Apache and Pinot and then analysed the numEntriesScannedInFilter and ... Now it's time to do some range querying....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
in that example query we went from 50 ms to 10 ms
after upgrading pinot and making the above change i can confirm that the above query now is not only faster but
numEntriesScannedInFilter
went from > than a mill to 0.thank you so much @richardstartin and @kishoreg