[LUCENE-5565] Remove String based encoding from SpatialPrefixTree/Cell API; just use bytes

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.8, 6.0
• Component/s: modules/spatial
• Lucene Fields: New
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 01/Apr/14 20:44
• Updated: 28/Aug/22 14:04
• Resolved: 04/Apr/14 16:30

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.

Issue Links

• is related to: LUCENE-5608 SpatialPrefixTree API refactor