[
https://issues.apache.org/jira/browse/LUCENE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318679#comment-15318679
]
Adrien Grand commented on LUCENE-7314:
--------------------------------------
The idea of putting solid + commonly useful features in core works for me, it
would probably be more user-friendly indeed. But it looks different from what
seemed to me to be the consensus (or maybe I misunderstood what it was!) until
now, ie. only having the common denominator in core and then having on module
per "feature" like highlighting, geo search or joins.
I am +0 on moving these classes to core. I initially thought this is something
we could do for 6.1 but since it proved a bit controversial, I suggest that we
only move classes for 6.2.
> 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]
