[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631963#action_12631963
]
Yonik Seeley commented on SOLR-773:
-----------------------------------
I haven't yet looked at the contributions (but I did read the whitepaper).
It seems like we want lat+lon in the same field value. That will remove the
need for any other mechanism to correlate the two (what lat goes with what lon)
and will allow future indexing mechanisms that operate on both values at once.
Do we need a new basic output type (in addition to str, int, long, etc)? For
now perhaps we should just use a string representation?
<str name="my_house">12.345,-67.89</str>
or in JSON
"my_house":"12.345,-67.89"
So breaking things down, it seems like we basically need to be able to:
1) filter by a bounding box
2) filter by a geo radius (impl could first get the bounding box and narrow
within that...)
3) sort by distance
4) return the distance
It also seems like there could be an opportunity to make much/most of this
generic (not specific to geosearch).
> Incorporate Local Lucene/Solr
> -----------------------------
>
> Key: SOLR-773
> URL: https://issues.apache.org/jira/browse/SOLR-773
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Priority: Minor
>
> Local Lucene has been donated to the Lucene project. It has some Solr
> components, but we should evaluate how best to incorporate it into Solr.
> See http://lucene.markmail.org/message/orzro22sqdj3wows?q=LocalLucene
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
