Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently the TransactionAwareHTable implementations track change sets at the column level. However, when using row-level conflict detection, we only need to track change sets at the granularity needed to be able to efficiently rollback failed transactions with version-specific deletes. For HBase 0.96+, this means at the column family-level, since deletes support specific versions at the family level.
This will minimize the change set that must be retained by the client.