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

GeoPointField should cut over to DocValues for boundary filtering

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.3, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Currently GeoPointField queries only use the Terms Dictionary for ranges that fall within and on the boundary of the query shape. For boundary ranges the full precision terms are iterated, for within ranges the postings list is used.

      Instead of iterating full precision terms for boundary ranges, this enhancement cuts over to DocValues for post-filtering boundary terms. This allows us to increase precisionStep for GeoPointField thereby reducing the number of terms and the size of the index. This enhancement should also provide a boost in query performance since visiting more docs and fewer terms should be more efficient than visiting fewer docs and more terms.

        Attachments

        1. LUCENE-6712.patch
          15 kB
          Nicholas Knize
        2. LUCENE-6712.patch
          19 kB
          Nicholas Knize
        3. LUCENE-6712.patch
          31 kB
          Nicholas Knize

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              nknize Nicholas Knize
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: