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

GeoPointDistanceRangeQuery not valid for multi-valued docs

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • None
    • 6.0, 6.1, 7.0
    • None
    • None
    • New

    Description

      This query currently takes minimum and maximum range and rewrites to a boolean query of two distance queries (big NOT little).

      The problem is, this rewrite is not correct if a document has multiple values in the field.

      Do we really need to support this query? What is the use case? Is it a relic of people doing things like pagination or distance faceting in a very slow way? We can do these things more efficiently with other mechanisms (e.g. distance sort for LatLonPoint works well with searchAfter, can be ported to geopoint).

      Attachments

        1. LUCENE-7126.patch
          14 kB
          Robert Muir

        Activity

          People

            Unassigned Unassigned
            rcmuir Robert Muir
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: