[LUCENE-6481] Improve GeoPointField type to only visit high precision boundary terms

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.3, 6.0
• Component/s: core/index
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Nick Knize
• Created: 13/May/15 17:34
• Updated: 28/Aug/22 14:32
• Resolved: 08/Jun/15 21:49

Description

Current GeoPointField 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.

Issue Links

• duplicates: LUCENE-6450 Add simple encoded GeoPointField type to core