[
https://issues.apache.org/jira/browse/LUCENE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419550#comment-17419550
]
ASF subversion and git services commented on LUCENE-10119:
----------------------------------------------------------
Commit da0e8822335c89e7cd797d2f81bfd109459d1676 in lucene-solr's branch
refs/heads/branch_8_10 from Nhat Nguyen
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=da0e882 ]
LUCENE-10119: Do not set single sort with search after
We should not set single sort when the search_after is non-null;
otherwise, we will incorrectly skip documents whose values are equal to
the value from the search_after and docIDs are greater than the docID
from the search_after.
> singleSort should not be set when after is non-null
> ---------------------------------------------------
>
> Key: LUCENE-10119
> URL: https://issues.apache.org/jira/browse/LUCENE-10119
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: main (9.0), 8.10
> Reporter: Nhat Nguyen
> Assignee: Nhat Nguyen
> Priority: Major
> Fix For: main (9.0), 8.11, 8.10.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Today we set the parameter `singleSort` to true when we have a single
> comparator to skip documents whose values equal the last visited value.
> However, this is incorrect when the search_after parameter is non-null as
> that we will skip documents whose values are equal, but their docIDs are
> greater than the docID of the `search_after` parameter.
>
> We found this issue in Elasticsearch after upgrading it to Lucene 8.10 and
> Lucene 9.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
