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

Remove String based encoding from SpatialPrefixTree/Cell API; just use bytes

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.8, 6.0
    • modules/spatial
    • None
    • New

    Description

      The SpatialPrefixTree/Cell API supports bytes and String encoding/decoding dually. I want to remove the String side to keep the API simpler. Included in this issue, I'd like to make some small refactorings to reduce assumptions the filters make of the underlying encoding such that future encodings can work a in more different ways with less impact on the filters.

      String encode/decode will exist for the Geohash one for now since GeohashUtils works off of Strings, but Quad could change more easily.

      Attachments

        Issue Links

          Activity

            People

              dsmiley David Smiley
              dsmiley David Smiley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: