Details
-
Brainstorming
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
In HBASE-14070 and HBASE-18642, we discuss using HLC and deprecating the client from being able to set timestamps for mutations. However, one important use case for setting the timestamps (which represent transaction IDs) is for transactions. What we could do is add a transaction ID to the result object that is the hybrid logical timestamp of a particular batch operation. The transaction ID should be considered opaque and clients should not make assumptions for how the ID is changed.
This change would be similar to the way Couchbase uses HLC where the timestamp of a mutation (denoted CAS) is stored in the result and sent back to the client.