[
https://issues.apache.org/jira/browse/LUCENE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239908#comment-15239908
]
Karl Wright commented on LUCENE-7212:
-------------------------------------
bq. Well i dont think we should do "prebuilt queries". If its expensive to do
up-front stuff this should be part of the cost. 2D has a prebuilding too at the
moment, it happens in createWeight though. But to an end user, its still
latency.
It's latency that can be controlled, though - the typical use case for very
large polygons is for them to be associated with countries etc., and there are
not many of those, and they can be prebuilt. So I think it is worth
considering the two costs separately.
I can make polygon building *much* faster if I know that you are handing me
well-formed convex polygons (or concave ones). The time comes from tiling
irregular polygons in a way that doesn't violate convexity/concavity
constraints. But that changes the API quite a bit then. :-)
> 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]
