[
https://issues.apache.org/jira/browse/LUCENE-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061986#comment-15061986
]
Adrien Grand commented on LUCENE-6926:
--------------------------------------
Thanks Paul, I see what you meant now and I agree with your conclusion that it
is not practical. This reminds me of a related idea that I had some time ago
that some scorers return bitset-based iterators, which could easily be NOT'ed
by using nextClearBit instead of nextSetBit so that we could apply them as a
required clause (which should perform better) instead of a prohibited clause.
I'll commit the patch shortly.
> 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
> Attachments: LUCENE-6926.patch, LUCENE-6926.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
