Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
None
-
None
-
None
-
None
Description
This has been discussed previously, and Lars H. was mentioning an idea from the client to declare whether timestamps are used or not explicitly.
The problem is that, for data models not using timestamps, we are still relying on clocks to order the updates. Clock skew, same milisecond puts after deletes, etc can cause unexpected behavior and data not being visible.
We should have a table descriptor / family property, which would declare that the data model does not use timestamps. Then we can populate this dimension with the seqId, so that global ordering of edits are not effected by wall clock.
For example, META will use this.
Once we have something like this, we can think of making it default for new tables, so that the unknowing user will not shoot herself in the foot.
Attachments
Attachments
Issue Links
- is related to
-
HBASE-8770 deletes and puts with the same ts should be resolved according to mvcc/seqNum
- Closed
-
HBASE-10247 Client promises about timestamps
- Closed
- relates to
-
HBASE-14070 Hybrid Logical Clocks for HBase
- Reopened
-
HBASE-8763 Combine MVCC and SeqId
- Closed