You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2015/12/10 20:45:11 UTC
[jira] [Updated] (LUCENE-6926) Take matchCost into account for
MUST_NOT clauses
[ https://issues.apache.org/jira/browse/LUCENE-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand updated LUCENE-6926:
---------------------------------
Description: ReqExclScorer potentially has two TwoPhaseIterators to check: the one for the positive clause and the one for the negative clause. It should leverage the match cost API to check the least costly one first.
> Take matchCost into account for MUST_NOT clauses
> ------------------------------------------------
>
> Key: LUCENE-6926
> URL: https://issues.apache.org/jira/browse/LUCENE-6926
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
>
> ReqExclScorer potentially has two TwoPhaseIterators to check: the one for the positive clause and the one for the negative clause. It should leverage the match cost API to check the least costly one first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org