[HBASE-493] Write-If-Not-Modified-Since support

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.90.0
• Component/s: Client, io, regionserver
• Assignee: Unassigned
• Reporter: Chris Richard
• Created: 05/Mar/08 19:00
• Updated: 11/Jun/22 20:13
• Resolved: 08/Jun/14 21:51

Description

Write-If-Not-Modified-Since for optimistic concurrency control:

Client retrieves cell (or row) and stores timestamp.
Client writes to same cell (or row) and passes timestamp.
If the cell's (or row's) latest timestamp matches the passed timestamp, the write succeeds. If the timestamps do not match, the write fails and the client is notified. The client must re-retrieve the cell/row to get the latest timestamp before attempting to write back.

This behavior would be optional, if the client doesn't pass a timestamp to the write method, no modified check would be enforced.

Note: blocked behind HBASE-489 due to requirement that client be able to access timestamp values.

Issue Links

• is blocked by: HBASE-489 CellValue class for transporting cell timestamp with cell value simultaneously
• is part of: HBASE-798 Provide Client API to explicitly lock and unlock rows
• is related to: HBASE-798 Provide Client API to explicitly lock and unlock rows
• is related to: HBASE-803 Atomic increment operations
• relates to: HBASE-669 MultiRegion transactions with Optimistic Concurrency Control