[HBASE-8462] Custom timestamps should not be allowed to be negative

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.96.0
• Component/s: Client
• Hadoop Flags: Reviewed
• Release Note: Timestamps in Mutations (Put/Delete, etc) are not allowed to be negative throwing IllegalArgumentException from the client side. Note that negative timestamps are not sorted correctly, and will cause inconsistencies when accessing the values.
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 30/Apr/13 01:54
• Updated: 20/Nov/15 11:55
• Resolved: 28/Aug/13 18:43

Description

Client supplied timestamps should not be allowed to be negative, otherwise unpredictable results will follow. Especially, since we are encoding the ts using Bytes.Bytes(long), negative timestamps are sorted after positive ones. Plus, the new PB messages define ts' as uint64.

Credit goes to Huned Lokhandwala for reporting this.

Issue Links

• is a clone of: HBASE-3293 Negative timestamps can be inserted without fail but not read again