[
https://issues.apache.org/jira/browse/LUCENE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318317#comment-15318317
]
Michael McCandless commented on LUCENE-7314:
--------------------------------------------
Here's a timely email by an unlucky user struggling to figure out how to do
spatial polygon search with Lucene: http://markmail.org/thread/mpge4wqo7cfqm4i5
(sent on June 4, 2016, with subject "Point in polygon" search with Lucene /
Spatial4j / JTS").
This email shows precisely why I think it's important that Lucene present good
default choices for common search use cases like spatial, highlighting, query
parsing, etc., and why I feel {{LatLonPoint}} in particular (this issue) should
move to Lucene's core.
It's clearly important we make Lucene easier to use for the common use cases
and by hiding away {{LatLonPoint}} in the spatial module, here, we fail to do
that.
A choice quote from the email:
{noformat}
I’ve spent more time figuring this out than I thought I’d have to and think I
must be missing something obvious, and am wondering if someone can help me out.
{noformat}
> 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]
