[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240287#comment-15240287
]
Robert Muir commented on LUCENE-7212:
-------------------------------------
I don't think the SortField/Comparator would change at all. Its just if we can
make polygon queries not need a "two-phase crutch" then docvalues are no longer
needed for queries. So we'd add something like LatLonDocValuesField (ugh, will
mull on the name) and move the newSortField() method to it, and turn off the
docvalues in LatLonPoint: its no longer needed for queries.
newSortField() and any other docvalues-oriented methods (e.g. getting a
LUCENE-5325 "stream" of latitudes or longitudes for expressions integration)
would be on that LatLonDocValuesField: it just concerns itself with docvalues,
and the LatLonPoint just concerns itself with the points stuff.
Just like the separation of DoublePoint vs DoubleDocValuesField in core/.
> 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]
