lucene-dev mailing list archives

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

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

Robert Muir commented on LUCENE-7147:
-------------------------------------

Dawid I think you are confused. People tend to do more than one query against an index :)

This optimization was here in spatial before: i removed it in LUCENE-7127 because it was broken.
Ryan just adds it back.

I see the following change:
sandbox/LatLonPoint: 17.2 QPS -> 26.3 QPS
spatial/GeoPointField: 12.8 QPS -> 16.3 QPS

Thanks ryan, +1

> 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