lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-7147) Improve disjoint check for geo distance query traversal
Date Tue, 29 Mar 2016 11:00:29 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215839#comment-15215839
] 

Karl Wright commented on LUCENE-7147:
-------------------------------------

[~mikemccand] For comparison, do you remember what is the equivalent geo3d timing?  I think
this is a case where 2D is likely better than 3D.  It's not because of the ability to properly
calculate intersections, but rather because there are three dimensions to descend into, and
because the intersection math is more expensive.

> Improve disjoint check for geo distance query traversal
> -------------------------------------------------------
>
>                 Key: LUCENE-7147
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7147
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Ryan Ernst
>         Attachments: LUCENE-7147.patch
>
>
> When doing geo distance queries, it is important to avoid traversing subtrees which do
not contain any relevant points. We currently have checks which compare the bbox of the query
to the bounds of the subtree. However, it is possible for a subtree to overlap the bbox, but
still not intersect the query. This issue is to improve that check to avoid unnecessary traversals.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message