[
https://issues.apache.org/jira/browse/LUCENE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318518#comment-15318518
]
David Smiley commented on LUCENE-7314:
--------------------------------------
RE the user's email: It does illustrate how much simpler LatLonPoint (and
GeoPointField, and probably the Geo3D one) are to use than the stuff in
spatial-extras with its multi-layer dependencies. Good work to all those that
helped make this possible! And now the more complicated spatial is put off to
the side in "spatial-extras". Users looking at Lucene fresh will surely look
in "spatial" for spatial stuff first before looking in other spatial modules,
and I believe before looking in Lucene-core. I mean... if we have spatial
module(s), who would think to go looking in core? We have other modules that
have their stuff apart in their own modules so I don't see why a user would
expect any different for spatial. I think we should furthermore add a bit of
documentation to the spatial module, spatial-extras module, to LatLonPoint, and
perhaps to GeoPointField to expressly point to LatLonPoint as the go-to
recommended spatial implementation.
RE compact1/compact2: I am not familiar with this stuff. Are you saying that
only Lucene-core will even work on a mobile device? If so that sucks... maybe
the spatial module should be compiled with compact1 too! Let this be a goal to
do what we need to do to our modules so that as many as reasonably can can get
to be compiled with compact1.
> Graduate InetAddressPoint and LatLonPoint to core
> -------------------------------------------------
>
> Key: LUCENE-7314
> URL: https://issues.apache.org/jira/browse/LUCENE-7314
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
>
> Maybe we should graduate these fields (and related queries) to core for
> Lucene 6.1?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
