[
https://issues.apache.org/jira/browse/LUCENE-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Vera resolved LUCENE-9273.
----------------------------------
Fix Version/s: 8.6
Assignee: Ignacio Vera
Resolution: Fixed
> 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
> Assignee: Ignacio Vera
> Priority: Major
> Fix For: 8.6
>
> 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]
