[
https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553494#comment-17553494
]
Adrien Grand commented on LUCENE-10480:
---------------------------------------
Good question, looking at your BlockMaxMaxScoreScorer it looks like it also has
potential for being specialized in the 2-clauses case by having two sub scorers
and tracking during document collection whether the scorer that produces lower
scores is optional or required. I didn't have concrete plans in mind when
opening the issue, I was just observing that we pay significant overhead for
supporting arbitrary numbers of clauses when disjunctions often have only two
clauses.
> Specialize 2-clauses disjunctions
> ---------------------------------
>
> Key: LUCENE-10480
> URL: https://issues.apache.org/jira/browse/LUCENE-10480
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
>
> WANDScorer is nice, but it also has lots of overhead to maintain its
> invariants: one linked list for the current candidates, one priority queue of
> scorers that are behind, another one for scorers that are ahead. All this
> could be simplified in the 2-clauses case, which feels worth specializing for
> as it's very common that end users enter queries that only have two terms?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
