[
https://issues.apache.org/jira/browse/LUCENE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685543#comment-16685543
]
Nicholas Knize commented on LUCENE-8554:
----------------------------------------
Just pointing out there was a nice performance improvement side effect from
this patch:
Seen here in
[geobench.html#search-polyMedium|http://people.apache.org/~mikemccand/geobench.html#search-polyMedium]
A simple optimization was added to
[EdgeTree.java#330|https://github.com/apache/lucene-solr/blob/95d01c6583b825b6b87591e4f27002c285ea25fb/lucene/core/src/java/org/apache/lucene/geo/EdgeTree.java#L330]
to check if either end of the polygon's line segment is contained by the
target rectangle. This optimization skips all of the determinant calculations
below giving what appears to be a boost in search performance of ~1.4 QPS for
{{LatLonPoint#newPolygonQuery}}
> Add new LatLonShapeLineQuery
> ----------------------------
>
> Key: LUCENE-8554
> URL: https://issues.apache.org/jira/browse/LUCENE-8554
> Project: Lucene - Core
> Issue Type: New Feature
> Affects Versions: 7.6, master (8.0)
> Reporter: Nicholas Knize
> Assignee: Nicholas Knize
> Priority: Blocker
> Attachments: LUCENE-8554.patch, LUCENE-8554.patch
>
>
> Its often useful to be able to query a shape index for documents that either
> {{INTERSECT}} or are {{DISJOINT}} from a given {{LINESTRING}}. Occasionally
> the linestring of interest may also have a distance component, which creates
> a *buffered query* (often used in routing, or shape snapping). This feature
> first adds a new {{LatLonShapeLineQuery}} for querying {{LatLonShape}}
> fields by arbitrary lines. A distance component can then be added in a future
> issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
