Order LeafReaderContexts by Estimated Number Of Hits [LUCENE-8788]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
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.
---
Migrated from [LUCENE-8788](https://issues.apache.org/jira/browse/LUCENE-8788) by Atri Sharma (@atris), updated May 24 2019
Contributor guide
Research direction
No file or test is named. Start by tracing how IndexSearcher visits LeafReaderContexts during searches, then determine how estimated hit counts and early termination should affect segment ordering; done means partial results are more relevant under the proposed ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100