[BEAM-5487] ByteKeyRangeTracker restrictions do not cover the entire interval because of incorrect next key

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.8.0
• Component/s: sdk-java-core
• Labels: Done
• Assignee: Luke Cwik
• Reporter: Luke Cwik
• Created: 24/Sep/18 20:25
• Updated: 06/Oct/20 21:52
• Resolved: 01/Oct/18 15:03

Description

The definition of next for a byte key is incorrectly set as old key + 1 when treating the key as the next smallest value, for example

0x01 is the next key for 0x00

 

The ByteKey compareTo operator treats two keys where one key is the proper prefix of the other as smaller hence 0x01 is greater then 0x00, but so is 0x0000 thus next is skipping over 0x0000 as the next smallest key larger then 0x00.

Issue Links

• breaks: BEAM-4018 Add a ByteKeyRangeTracker based on RestrictionTracker for SDF
• links to: GitHub Pull Request #6481