[
https://issues.apache.org/jira/browse/LUCENE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315521#comment-15315521
]
David Smiley commented on LUCENE-7314:
--------------------------------------
Mike: Sorry but I see this quite different than codecs. Lucene's Codec API is
the foundation of Lucene. In order for Lucene-core to function by itself, it
_requires_ at least one codec impl to do anything at all. And so we need to
have at least one impl in Lucene-core. This obviously isn't similar to
LatLonPoint at all. RE our other modules, you suggest they exist for
"expert/experimental/less-back-compat-guarantee implementations" -- to, I think
you mean to imply, things in Lucene-core. But of course this isn't true. We
don't have a default highlighter or default suggester or default join, or etc.
in Lucene core. I feel like I'm in some weird dream in which smart people that
I respect say things that make no sense to me, making me wonder if I've gone
crazy.
[~jpountz] can you post your rationale from your perspective? (You're the o.p.
after all)
I want to solicit input from others committers active in Lucene that don't
typically give their input on anything spatial. [~thetaphi] [~romseygeek] can
you please share your thoughts on this discussion? Specifically, where should
LatLonPoint go and why? And likewise for InetAddressPoint. I suggested "misc"
for that one but haven't gotten a reaction to that yet.
> 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]
