[
https://issues.apache.org/jira/browse/LUCENE-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240984#comment-15240984
]
Robert Muir commented on LUCENE-7069:
-------------------------------------
Do we really need NearestHit? I dont think we should add this class.
We created the FieldDoc nightmare, we should live with it? Distance sort
already has to live with its crappiness.
We should just fix that separately so its less horrible, but i dont think
inventing extra classes for different use cases is a better solution?
> Add LatLonPoint.nearest to find closest indexed point to a given query point
> ----------------------------------------------------------------------------
>
> Key: LUCENE-7069
> URL: https://issues.apache.org/jira/browse/LUCENE-7069
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: master, 6.1
>
> Attachments: LUCENE-7069.patch, LUCENE-7069.patch, LUCENE-7069.patch
>
>
> KD trees (used by Lucene's new dimensional points) excel at finding "nearest
> neighbors" to a given query point ... I think we should add this to Lucene's
> sandbox as:
> {noformat}
> public static Document nearest(IndexReader r, String field, double lat,
> double lon) throws IOException
> {noformat}
> I only implemented the 1 nearest neighbor for starters ... I think we can
> easily generalize this in the future to K nearest.
> It could also be generalized to more than 2 dimensions, but for now I'm
> making the class package private in sandbox for just the geo2d (lat/lon) use
> case.
> I don't think this should go into 6.0.0, but should go into 6.1: it's a new
> feature, and we need to wrap up and ship 6.0.0 already ;)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
