lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8788) Order LeafReaderContexts by Estimated Number Of Hits
Date Tue, 21 May 2019 13:03:00 GMT


Atri Sharma commented on LUCENE-8788:

[~jpountz] Yes, that is precisely the idea i.e. "learning" from previous collections to take
decisions for the next set of collections. We can batch up slices into "familiies" i.e. set
of sets, and each set is collected in sequential manner with shared metastate like you described
above. We could potentially collect multiple families in parallel. WDYT?


Thanks for validating the idea. I will work on a PoC patch now.

I like the idea [~jim.ferenczi] proposed. I can open a Jira for that and work on a patch
for it as well, unless Jim wants to do it himself?

> Order LeafReaderContexts by Estimated Number Of Hits
> ----------------------------------------------------
>                 Key: LUCENE-8788
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Atri Sharma
>            Priority: Major
> We offer no guarantee on the order in which an IndexSearcher will look at segments during
a search operation. This can be improved for use cases where an engine using Lucene invokes
early termination and uses the partially collected hits. A better model would be if we sorted
segments by the estimated number of hits, thus increasing the probability of the overall relevance
of the returned partial results.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message