[
https://issues.apache.org/jira/browse/LUCENE-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058762#comment-15058762
]
Paul Elschot commented on LUCENE-6926:
--------------------------------------
I tried implementing this NOT wrapper, but it is not feasible because the
nextDoc() implementation will have to do a linear scan as long as the wrapped
iterator provides consecutive docs.
So this might be nice in theory, but it will not perform well.
That means that I can't easily improve on the latest patch, it looks good, and
core tests pass here.
> 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]
