You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Nhat Nguyen (Jira)" <ji...@apache.org> on 2021/09/24 02:14:00 UTC
[jira] [Updated] (LUCENE-10119) singleSort should not be set when
after is non-null
[ https://issues.apache.org/jira/browse/LUCENE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nhat Nguyen updated LUCENE-10119:
---------------------------------
Fix Version/s: 8.11
main (9.0)
> 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
>
> Time Spent: 1h 20m
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org