Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-10119

singleSort should not be set when after is non-null

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 9.0, 8.10
    • 9.0, 8.11, 8.10.1
    • core/search
    • None
    • New

    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.

      Attachments

        Activity

          People

            dnhatn Nhat Nguyen
            dnhatn Nhat Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1.5h
                1.5h