[
https://issues.apache.org/jira/browse/LUCENE-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973697#comment-13973697
]
David Smiley commented on LUCENE-5565:
--------------------------------------
I'm going to back this out of branch 4x (and thus 4.8) because I (now) view it
one incremental step of a larger thing which is LUCENE-5608 (SPT API refactor).
LUCENE-5608 won't make it into 4.8 so better to not see it partway done and
get released. In fact LUCENE-5608 shouldn't be backported to 4x until at least
one new SPT uses the API, which may trigger some changes to the new API.
> Remove String based encoding from SpatialPrefixTree/Cell API; just use bytes
> ----------------------------------------------------------------------------
>
> Key: LUCENE-5565
> URL: https://issues.apache.org/jira/browse/LUCENE-5565
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 4.8, 5.0
>
> Attachments: LUCENE-5565_SPT_remove_String.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
