[
https://issues.apache.org/jira/browse/LUCENE-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871543#comment-16871543
]
Atri Sharma commented on LUCENE-8875:
-------------------------------------
While I do agree that too many hits are not what top N hits are intended for,
but some increasing popular use cases are inclined in that direction (bucket
aggregates?) I think it would be fair to allow such users to use a different
Collector which optimises their case while not muddling with the commonly used
code path. WDYT?
> Should TopScoreDocCollector Always Populate Sentinel Values?
> ------------------------------------------------------------
>
> Key: LUCENE-8875
> URL: https://issues.apache.org/jira/browse/LUCENE-8875
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
>
> TopScoreDocCollector always initializes HitQueue as the PQ implementation,
> and instruct HitQueue to populate with sentinels. While this is a great
> safety mechanism, for very large datasets where the query's selectivity is
> high, the sentinel population can be redundant and can become a large enough
> bottleneck in itself. Does it make sense to introduce a new parameter in
> TopScoreDocCollector which uses a heuristic (say number of hits > 10k) and
> does not populate sentinels?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
