[LUCENE-10119] singleSort should not be set when after is non-null

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.0, 8.10
• Fix Version/s: 9.0, 8.11, 8.10.1
• Component/s: core/search
• Lucene Fields: New
• Assignee: Nhat Nguyen
• Reporter: Nhat Nguyen
• Created: 23/Sep/21 03:10
• Updated: 28/Aug/22 16:26
• Resolved: 24/Sep/21 03:34

Description

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.

Issue Links

• links to: GitHub Pull Request #317
• links to: GitHub Pull Request #2582
• links to: GitHub Pull Request #2583