[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243105#comment-15243105
]
Robert Muir commented on LUCENE-7212:
-------------------------------------
ok but #2 should take some time. i sorta see it as really important "sandiness"
to fix though :). in the meantime if you want to proceed with 3D, and come up
with e.g. a 64-bit encoding, I can help get the docvalues field together or
whatever you need.
As far as if #1 is crucial, i think you have to do some experiments to find
out? In 2D we know the bounding box check is a big win. This optimization is a
very tricky balance because computing that is itself expensive, and users do
crazy things (sort with enormous top N's or somehow data could be in
adversarial sort order causing shittons of priority queue updates). The
situation for 3D may be different.
> 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]
