[
https://issues.apache.org/jira/browse/LUCENE-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138678#comment-16138678
]
ASF subversion and git services commented on LUCENE-7939:
---------------------------------------------------------
Commit 3be5808caf0235081aa47b3604e00d3b5f358d80 in lucene-solr's branch
refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3be5808 ]
LUCENE-7939: Speed up MinShouldMatchSumScorer in conjunctions.
> Speed up MinShouldMatchSumScorer in conjunctions
> ------------------------------------------------
>
> Key: LUCENE-7939
> URL: https://issues.apache.org/jira/browse/LUCENE-7939
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: master (8.0), 7.1
>
> Attachments: LUCENE-7939.patch, LUCENE-7939.patch
>
>
> MinShouldMatchSumScorer has good iteration capabilities, but if it is not
> used as a lead for the iteration then the advance() call might make a lot of
> efforts in order to find the next match while we should instead let the lead
> iterator of the conjunction skip over non-matching documents. In this issue
> I'd like to explore changing MinShouldMatchSumScorer by giving it a two-phase
> iterator and making advance() return a candidate for the next match that is
> less good but much cheaper to compute.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
