[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240261#comment-15240261
]
Robert Muir commented on LUCENE-7212:
-------------------------------------
Yeah, for this issue, it would be great to just confirm the cost is really an
up-front issue for polygons. As long as we are confident in that (and it looks
that way to me), then we can continue here unblocked.
I have the feeling thats all it is, and that Geo3D doesn't really need
two-phase iteration. (Hopefully 2D won't need it either, if it can clean up its
polygon act to not be trappy).
So I think this issue can just focus on docvalues for distance?
As far as LatLonPoint goes, if we can remove the need for it to use docvalues
in polygon queries, I think its better to have a separate *Field for going into
docvalues.
It means that the docvalues become optional, just like they are for the other
fields in lucene. You add it to your doc too if you want sorting, faceting,
expressions, etc, but you don't need it if you are just doing searches, and
vice-versa: you don't need the multi-dimensional ports index if you are just
doing sorting/faceting/expressions. so the DocValues field really is a
completely unrelated thing. We might want to do it the same way for 3D.
> 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]
