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

Decouple GeoPointField from NumericType

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Done
    • None
    • trunk, 5.5
    • modules/spatial
    • None
    • New

    Description

      GeoPointField currently relies on NumericTokenStream to create prefix terms for a GeoPoint using the precision step defined in GeoPointField. At search time GeoPointTermsEnum recurses to a max precision that is computed by the Query parameters. This max precision is never the full precision, so creating and indexing the full precision terms is useless and wasteful (it was always a side effect of just using indexing logic from the Numeric type).

      Furthermore, since the numerical logic always stored high precision terms first, the recursion in GeoPointTermsEnum required transient memory for storing ranges. By moving the trie logic to its own GeoPointTokenStream and reversing the term order (such that lower resolution terms are first), the GeoPointTermsEnum can naturally traverse, enabling on-demand creation of PrefixTerms. This will be done in a separate issue.

      Attachments

        1. LUCENE-6930.patch
          117 kB
          Nick Knize
        2. LUCENE-6930.patch
          115 kB
          Nick Knize
        3. LUCENE-6930.patch
          121 kB
          Nick Knize
        4. LUCENE-6930.patch
          120 kB
          Nick Knize
        5. LUCENE-6930.patch
          100 kB
          Nick Knize
        6. LUCENE-6930.patch
          84 kB
          Nick Knize

        Activity

          People

            Unassigned Unassigned
            nknize Nick Knize
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: