You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Ignacio Vera (Jira)" <ji...@apache.org> on 2019/10/04 05:36:00 UTC

[jira] [Resolved] (LUCENE-8860) LatLonShapeBoundingBoxQuery could make more decisions on inner nodes

     [ https://issues.apache.org/jira/browse/LUCENE-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignacio Vera resolved LUCENE-8860.
----------------------------------
    Fix Version/s: 8.3
         Assignee: Ignacio Vera
       Resolution: Fixed

Thanks [~imotov]!

> LatLonShapeBoundingBoxQuery could make more decisions on inner nodes
> --------------------------------------------------------------------
>
>                 Key: LUCENE-8860
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8860
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Ignacio Vera
>            Priority: Minor
>             Fix For: 8.3
>
>         Attachments: fig1.png, fig2.png, fig3.png
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently LatLonShapeBoundingBoxQuery with the INTERSECTS relation only returns CELL_INSIDE_QUERY if the query contains ALL minimum bounding rectangles of the indexed triangles.
> I think we could return CELL_INSIDE_QUERY if the box contains either of the edges of all MBRs of indexed triangles since triangles are guaranteed to touch all edges of their MBR by definition. In some cases this would help save decoding triangles and running costly point-in-triangle computations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org