[LUCENE-10262] Lift up restrictions for navigating PointValues#PointTree

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.1
• Lucene Fields: New
• Assignee: Ignacio Vera
• Reporter: Ignacio Vera
• Created: 25/Nov/21 11:02
• Updated: 28/Aug/22 16:31
• Resolved: 26/Nov/21 06:45

Description

Following up LUCENE-9820, we currently do not allow some navigation combinations on the PointTree which might make a bit trappy to use it in some cases. For example we should be calling moveToChild after calling moveToParent.

I had a second thought and realise it can be very cheap to remove this limitation. We only need a new array of integers that holds the position when reading the node data in each level (very similar to what we are doing in rightNodePositions. Then we only need to check we are in the right position whenever we navigate down the tree.

Issue Links

• links to: GitHub Pull Request #476