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

NumericLeafComparator to define getPointValues

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 9.0, 8.11
    • None
    • None
    • New

    Description

      NumericLeafComparator must have a method getPointValues similar how it has getNumericDocValues.

      Numeric Sort optimization with points relies on the assumption that points and doc values record the same information, as we substitute iterator over doc_values with one over points.

      If we extend getNumericDocValues it almost certainly means that whatever PointValues NumericComparator is going to look at shouldn't be used to skip non-competitive documents. Returning null for pointValues in this case will force comparator NOT to use sort optimization with points, and continue with a traditional way of iterating over doc values.

      Attachments

        Activity

          People

            Unassigned Unassigned
            mayya Mayya Sharipova
            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 - 1h 50m
                1h 50m