[LUCENE-2184] CartesianPolyFilterBuilder doesn't properly account for which tiers actually exist in the index

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9, 2.9.1, 3.0
• Fix Version/s: 3.1, 4.0-ALPHA
• Component/s: modules/spatial
• Lucene Fields: New
• Assignee: Grant Ingersoll
• Reporter: Grant Ingersoll
• Created: 28/Dec/09 19:09
• Updated: 28/Aug/22 12:17
• Resolved: 27/Nov/10 23:25

Description

In the CartesianShapeFilterBuilder, there is logic that determines the "best fit" tier to create the Filter against. However, it does not account for which fields actually exist in the index when doing so. For instance, if you index tiers 1 through 10, but then choose a very small radius to restrict the space to, it will likely choose a tier like 15 or 16, which of course does not exist.