[HBASE-3584] Allow atomic put/delete in one call

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.94.0
• Component/s: Client, Coprocessors, regionserver
• Hadoop Flags: Reviewed
• Assignee: Lars Hofhansl
• Reporter: ryan rawson
• Created: 01/Mar/11 01:50
• Updated: 12/Oct/12 05:35
• Resolved: 14/Jan/12 05:00

Description

Right now we have the following calls:

put(Put)
delete(Delete)
increment(Increments)

But we cannot combine all of the above in a single call, complete with a single row lock. It would be nice to do that.

It would also allow us to do a CAS where we could do a put/increment if the check succeeded.

---

Amendment:
Since Increment does not currently support MVCC it cannot be included in an atomic operation.
So this for Put and Delete only.

Issue Links

• is part of: HBASE-3523 Rewrite our client (client 2.0)
• relates to: HBASE-5569 Do not collect deleted KVs when they are still in use by a scanner.

Sub-Tasks

• Group atomic put/delete operation into a single WALEdit to handle region server failures.: Closed
• Rename RowMutation to RowMutations: Closed
• Assign different memstoreTS to different KV's in the same WALEdit during replay: Open
• use different memstoreTS for different operations in the same RowMutation.: Open