[LUCENE-7845] spatial RPT optimization when query by point or common date range

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.0
• Component/s: modules/spatial-extras
• Lucene Fields: New
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 22/May/17 21:25
• Updated: 28/Aug/22 15:15
• Resolved: 05/Jun/17 16:47

Description

If the query to an RPT index is a 2D point, or if using NumerBrangePrefixTreeStrategy / DateRangePrefixTree (Solr DateRangeField) if the query is a grid cell (a common date range unit like some particular day), then we can do some optimizations, especially if the data is pointsOnly. If the data is pointsOnly the strategy can return a TermQuery, if the data isn't then we can at least tweak the prefixGridScanLevel. This is motivated by two scenarios:

• indexing polygons and doing lookups by a point (AKA reverse geocoding)
• indexing date instances and doing date range faceting. Solr's code for this has a fast path for a TermQuery, although more is needed beyond this issue to get there.

This development was funded by the Harvard Center for Geographic Analysis as part of the HHypermap project

Issue Links

• is broken by: LUCENE-7859 PackedQuadCell.getTokenBytesNoLeaf bug when null BytesRef