[
https://issues.apache.org/jira/browse/LUCENE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080764#comment-13080764
]
John Wang commented on LUCENE-3364:
-----------------------------------
Hi Paul:
I think adding score threshold to the nextDoc()/advance() apis would pollute
the filtering part of the API which has nothing to do with scoring. I do see
the spirit to allow for further skipping of docs given the score, however, a
simply if check in that loop may be a hinderance to performance. So I am not
sure if it is worth it.
Just my $0.02.
-John
> Add score threshold into Scorer.score()
> ---------------------------------------
>
> Key: LUCENE-3364
> URL: https://issues.apache.org/jira/browse/LUCENE-3364
> 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 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
