Shared Bottom Score Based Early Termination For Concurrent Search [LUCENE-8974]
Open
legacy-jira-priority:Major
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Following up to #9982, post collection of numHits, we should share a bottom score which can be used to globally filter hits and choose competitive hits
---
Migrated from [LUCENE-8974](https://issues.apache.org/jira/browse/LUCENE-8974) by Atri Sharma (@atris)
Contributor guide
Research direction
Start by reading the related issue #9982 and the concurrent search and post-collection behavior described here. Determine how numHits are collected and where a shared bottom score could globally filter hits and select competitive hits. Done means the concurrent search uses the shared score consistently, with behavior validated by appropriate search tests.
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
- 25/100