[LUCENE-3364] Add score threshold into Scorer.score()

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: core/query/scoring
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: John Wang
• Created: 06/Aug/11 17:45
• Updated: 28/Aug/22 12:55

Description

This is an optimization for scoring.
Given a Scorer.score() implementation, where features are gathered to calculate a score.

Proposal, add a parameter to score, e.g. score(float threshold)

This threshold is the minimum score to "beat" to make it to the current PriorityQueue. This could potential save a great deal of wasted calculation in the cases where recall is large.

In our case specifically, some of the features needed to do calculation can be expensive to obtain, it would be nice to have a place to decide whether or not even fetching these features are necessary.

Also, if we know the score would be low, simply threshold can be returned.

Let me know if this makes sense and I can work on a patch.