[LUCENE-2686] DisjunctionSumScorer should not call .score on sub scorers until consumer calls .score

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0-BETA, 6.0
• Component/s: core/search
• Lucene Fields: New
• Assignee: Michael McCandless
• Reporter: Michael McCandless
• Created: 04/Oct/10 17:16
• Updated: 28/Aug/22 12:33
• Resolved: 18/Jul/12 21:21

Description

Spinoff from java-user thread "question about Scorer.freq()" from Koji...

BooleanScorer2 uses DisjunctionSumScorer to score only-SHOULD-clause boolean queries.

But, this scorer does too much work for collectors that never call .score, because it scores while it's matching. It should only call .score on the subs when the caller calls its .score.

This also has the side effect of messing up advanced collectors that gather the freq() of the subs (using LUCENE-2590).

Issue Links

• breaks: LUCENE-2590 Enable access to the freq information in a Query's sub-scorers
• is related to: LUCENE-3505 BooleanScorer2.freq() doesnt work unless you call score() first.