[
https://issues.apache.org/jira/browse/LUCENE-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087943#comment-17087943
]
ASF subversion and git services commented on LUCENE-9273:
---------------------------------------------------------
Commit f914e08b3647ad91eb97ada6ebefe1e96ebd5a89 in lucene-solr's branch
refs/heads/master from Ignacio Vera
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f914e08 ]
LUCENE-9273: Speed up geometry queries by specialising Component2D spatial
operations (#1341)
Speed up geometry queries by specialising Component2D spatial operations.
Instead of using a generic relate method for all relations, we use specialise
methods for each one. In addition, the type of triangle is computed at
deserialisation time, therefore we can be more selective when decoding points
of a triangle
> Speed up geometry queries by specialising Component2D spatial operations
> ------------------------------------------------------------------------
>
> Key: LUCENE-9273
> URL: https://issues.apache.org/jira/browse/LUCENE-9273
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ignacio Vera
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is a follow-up from an observation of [~jpountz] where it notice that
> regardless of the spatial operation we are executing (e.g Intersects), we are
> always calling the method component2D#relateTriangle which it would be less
> expensive if we have an specialise method for intersects.
> The other frustrating thing is that regardless of the type of triangle we are
> dealing with, we are decoding all points of the triangle. In addicting most
> of the implementation of component2D#relateTriangle contain code that check
> the type of triangle to then call specialise methods.
> In this issue it is proposed to replace the method component2D#relateTriangle
> by the following methods:
> component2D#intersectsTriangle
> component2D#intersectsLine
> component2D#containsTriangle
> component2D#containsLine
> For consistency we add as well the methods:
> component2D#withinPoint
> component2D#withinLine
> Finally, the resolution of the triangle type his added to the decoding of the
> triangle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]