[
https://issues.apache.org/jira/browse/LUCENE-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732335#comment-16732335
]
David Smiley commented on LUCENE-8621:
--------------------------------------
BTW I already filed an issue to remove the spatial module and worked on it
including a patch but [~jpountz] wasn't sure about that since it seemed
LatLonShape would wind up there:
https://issues.apache.org/jira/browse/LUCENE-8369?focusedCommentId=16525475&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16525475
While I'm a fan of having either no spatial or simple spatial in lucene-core,
I'm also in favor of simplifying the user experience by reducing the number of
places they will find spatial stuff. Balancing the two, and given the slippery
slope of spatial already in lucene-core, I think it's best to remove the
spatial module and put LatLonShape into core.
> Move LatLonShape out of sandbox
> -------------------------------
>
> Key: LUCENE-8621
> URL: https://issues.apache.org/jira/browse/LUCENE-8621
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
>
> LatLonShape has matured a lot over the last months, I'd like to start
> thinking about moving it out of sandbox so that it doesn't stay there for too
> long like what happened to LatLonPoint. I am pretty happy with the current
> encoding. To my knowledge, we might just need to do a minor modification
> because of
> LUCENE-8620.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
