[LUCENE-1252] Avoid using positions when not all required terms are present

• Type: Wish
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Component/s: core/search
• Labels: gsoc2014
• Assignee: Unassigned
• Reporter: Paul Elschot
• Created: 29/Mar/08 08:56
• Updated: 28/Aug/22 11:48
• Resolved: 14/Feb/15 11:04

Description

In the Scorers of queries with (lots of) Phrases and/or (nested) Spans, currently next() and skipTo() will use position information even when other parts of the query cannot match because some required terms are not present.
This could be avoided by adding some methods to Scorer that relax the postcondition of next() and skipTo() to something like "all required terms are present, but no position info was checked yet", and implementing these methods for Scorers that do conjunctions: BooleanScorer, PhraseScorer, and SpanScorer/NearSpans.