[LUCENE-8928] BKDWriter could make splitting decisions based on the actual range of values

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 8.4
• Lucene Fields: New
• Assignee: Ignacio Vera
• Reporter: Adrien Grand
• Created: 19/Jul/19 08:56
• Updated: 28/Aug/22 15:49
• Resolved: 16/Oct/19 09:49

Description

Currently BKDWriter assumes that splitting on one dimension has no effect on values in other dimensions. While this may be ok for geo points, this is usually not true for ranges (or geo shapes, which are ranges too). Maybe we could get better indexing by re-computing the range of values on each dimension before making the choice of the split dimension?

Issue Links

• links to: GitHub Pull Request #926