[
https://issues.apache.org/jira/browse/LUCENE-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-6481:
-----------------------------------
Attachment: LUCENE-6481.patch
You can use the postings when the cell is wholly contained within the polygon,
which wasn't in that last patch. New patch attached to include this logic.
Boundary cells are still computed as they relate to the bbox. This could be
improved by computing boundary cells as they relate to the shape as long as
computing the existence of an intersection of the bbox and shape is fast - this
is usually the Achilles heel of spatial relations.
> Improve GeoPointField type to only visit high precision boundary terms
> -----------------------------------------------------------------------
>
> Key: LUCENE-6481
> URL: https://issues.apache.org/jira/browse/LUCENE-6481
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Nicholas Knize
> Attachments: LUCENE-6481.patch, LUCENE-6481.patch, LUCENE-6481.patch,
> LUCENE-6481.patch, LUCENE-6481.patch, LUCENE-6481.patch, LUCENE-6481_WIP.patch
>
>
> Current GeoPointField [LUCENE-6450 |
> https://issues.apache.org/jira/browse/LUCENE-6450] computes a set of ranges
> along the space-filling curve that represent a provided bounding box. This
> determines which terms to visit in the terms dictionary and which to skip.
> This is suboptimal for large bounding boxes as we may end up visiting all
> terms (which could be quite large).
> This incremental improvement is to improve GeoPointField to only visit high
> precision terms in boundary ranges and use the postings list for ranges that
> are completely within the target bounding box.
> A separate improvement is to switch over to auto-prefix and build an
> Automaton representing the bounding box. That can be tracked in a separate
> issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
