[
https://issues.apache.org/jira/browse/LUCENE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126925#comment-13126925
]
Uwe Schindler commented on LUCENE-3364:
---------------------------------------
LUCENE-1536 would only help if your filter supports random access and is not
too sparse (unless you override FilteredQuery.useRandomAccess() to always
return true). In all other cases, filters are applied iterative like in
previous versions. I just want to mention this.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
