lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3364) Add score threshold into Scorer.score()
Date Thu, 13 Oct 2011 19:05:12 GMT


Robert Muir commented on LUCENE-3364:

and just fyi, this method is only called if you are a top-level scorer (or inside a BooleanScorer,
but in that case the collector won't be "your collector")

it also currently wont be called if you do with a filter, but there are some efforts
to make it so you can control that (LUCENE-1536)

> Add score threshold into Scorer.score()
> ---------------------------------------
>                 Key: LUCENE-3364
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: core/query/scoring
>            Reporter: John Wang
> 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
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message