[HBASE-2286] [Transactional Contrib] Correctly handle or avoid cases where writes occur in same millisecond

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.90.0
• Hadoop Flags: Reviewed
• Assignee: Clint Morgan
• Reporter: Clint Morgan
• Created: 04/Mar/10 20:08
• Updated: 20/Nov/15 12:42
• Resolved: 07/Apr/10 23:50

Description

This patch fixes a few issues where puts/deletes occur with the same timestamp.

In the indexing layer, we avoid a Delete followed by a Put to the same row for the index update. When the row is the same, we can just do the put.

In the transactional layer, we correctly handled put, put, scan. This way the scan will see the last put, even if they have the same timestamp.

Remove the sleep to fix the putPutScan transactional test, and run it many times to be sure we hit the case where they are in the same millisecond.

Also some small cleanup, null handling, and fail-fast changes.