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

remove all encode/decode hooks from PointRangeQuery

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 6.0
    • None
    • None
    • New

    Description

      In LUCENE-7043 we added several new point types and just gave them static methods to generate exact/range/prefix/whatever queries.

      I think we should do the same in general, e.g. for IntPoint:

      This field defines static factory methods for creating common queries:
      <ul>
        <li>{@link #newExactQuery newExactQuery()} for matching an exact 1D point.
        <li>{@link #newRangeQuery newRangeQuery()} for matching a 1D range.
        <li>{@link #newMultiRangeQuery newMultiRangeQuery()} for matching points/ranges in n-dimensional space.
      </ul>
      

      Then each Point can have types that make sense for it: e.g. multi-dimensional range queries don't make sense at all for IP addresses, but prefix query does, and polygon/distance queries make sense for LatLonPoint and so on (that one is not refactored yet here, followup!)

      Attachments

        1. LUCENE-7045.patch
          106 kB
          Robert Muir

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: