[
https://issues.apache.org/jira/browse/LUCENE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314256#comment-15314256
]
Nicholas Knize commented on LUCENE-7314:
----------------------------------------
Well for the same reasons, prior to {{LatLonPoint}}, {{GeoPointField}} was
originally intended for core (several issues discussing this). But that kept
getting vetoed under the justification that spatial is a specialized use-case.
That's why the dependency free spatial module, and spatial-extras
discussion/refactor occurred, resulting in 3 different modules for spatial
types. I'd prefer avoid further fragmenting to 4 module locations. (Would
better prefer to collapse to 2 modules) But if the "special use-case" veto has
since majority lifted, I'll +0 to avoid another bikeshed and being "that
blocker guy". :)
> 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]
