[PHOENIX-1686] Data length should be checked in KeyValueSchema.next() and maxOffset should be set correctly by the caller

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.2.0
• Fix Version/s: 4.3.0
• Assignee: Wei Xue
• Reporter: Wei Xue
• Due: 27/Feb/15
• Created: 25/Feb/15 22:22
• Updated: 21/Nov/15 02:17
• Resolved: 07/Apr/15 00:38

Description

When decoding values from a KeyValueSchema data object, we should check that the length specified (either by its type of fixed length or by the length flag) does not exceed maxOffset.
Meanwhile, maxOffset should not be the total length of the ImmutableBytesWritable object, but instead should be the total length minus the length of the tailing valueSetBit.