[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239417#comment-15239417
]
Robert Muir commented on LUCENE-7212:
-------------------------------------
Also the encoding plays a role: to support sorting at all geo3d needs to figure
out how to encode it in docvalues.
Does geo3d also need two-phase query support? If so this also relates to how to
encode in docvalues (and whether its necessary or maybe should be optional or
any of that). We don't benchmark this at all, but it seems to be almost
necessary for 2D to meet user expectations, so 2D requires it. In other words a
distance or poly query may be slow, but if they restrict the dataset with other
filters then its less slower as it defers per-hit computations until its truly
needed. If this is not needed for 3D, it might simplify how to support sorting
as any encoding need only be geared at that.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
