[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239449#comment-15239449
]
Robert Muir commented on LUCENE-7212:
-------------------------------------
{quote}
It varies – that's one of the reasons there are different DistanceStyle
implementations. The cheapest (squared linear distance) is quite cheap; the
most expensive (arc distance) requires several Math.acos invocations (for a
path).
{quote}
I would start simple as mike suggests and not try to make a generic solution:
maybe just support one of them as a start. Sorting can be a real hotspot: look
at all the craziness the 2D one does to speed up/avoid haversin computations.
The best solution is very much tied to both the formula in question and the
underlying encoding.
> Add Geo3DPoint equivalents of LatLonPointDistanceComparator and
> LatLonPointSortField
> ------------------------------------------------------------------------------------
>
> Key: LUCENE-7212
> URL: https://issues.apache.org/jira/browse/LUCENE-7212
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: master
> Reporter: Karl Wright
> Assignee: Karl Wright
>
> Geo3D has a number of distance measurements and a generic way of computing
> interior distance. It would be great to take advantage of that for queries
> that return results ordered by interior distance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
