Specialize DisjunctionScorer if all clauses are TermQueries [LUCENE-3333]
Open
affects-version:4.0-ALPHA
legacy-jira-fix-version:4.9
legacy-jira-fix-version:6.0
legacy-jira-label:gsoc2014
legacy-jira-priority:Major
module:core/search
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
spinnoff from #4401 - since we have a specialized conjunction scorer we should also investigate if this pays off in disjunction scoring
---
Migrated from [LUCENE-3333](https://issues.apache.org/jira/browse/LUCENE-3333) by Simon Willnauer (@s1monw), 1 vote, updated May 09 2016
Contributor guide
Research direction
Start by reading issue #4401 and the migrated LUCENE-3333 discussion, then locate the existing specialized conjunction scorer and disjunction scoring entry points. No specific files or tests are named; done means establishing whether specializing DisjunctionScorer for all-TermQuery clauses is worthwhile and documenting the resulting scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100