You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jim Ferenczi (JIRA)" <ji...@apache.org> on 2018/08/07 08:01:00 UTC
[jira] [Updated] (LUCENE-8204) ReqOptSumScorer should leverage sub
scorers' per-block max scores
[ https://issues.apache.org/jira/browse/LUCENE-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Ferenczi updated LUCENE-8204:
---------------------------------
Attachment: LUCENE-8204.patch
> ReqOptSumScorer should leverage sub scorers' per-block max scores
> -----------------------------------------------------------------
>
> Key: LUCENE-8204
> URL: https://issues.apache.org/jira/browse/LUCENE-8204
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-8204.patch, LUCENE-8204.patch, LUCENE-8204.patch
>
>
> Currently it only looks at max scores on the entire segment. Given that per-block max scores usually give lower upper bounds of the score, this should help.
> This is especially important for LUCENE-8197 to work well since the main query would typically be added as a MUST clauses of a boolean query while the query that scores on features would be a SHOULD clause.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org