You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Phil Yang (JIRA)" <ji...@apache.org> on 2016/11/16 14:55:58 UTC
[jira] [Created] (HBASE-17112) Prevent setting timestamp of delta
operations being same as previous value's
Phil Yang created HBASE-17112:
---------------------------------
Summary: Prevent setting timestamp of delta operations being same as previous value's
Key: HBASE-17112
URL: https://issues.apache.org/jira/browse/HBASE-17112
Project: HBase
Issue Type: Bug
Reporter: Phil Yang
Assignee: Phil Yang
In delta operations, Increment and Append. We will read current value first and then write the new whole result into WAL as the type of Put with current timestamp. If the previous ts is larger than current ts, we will use the previous ts.
If we have two Puts with same TS, we will ignore the Put with lower sequence id. It is not friendly with versioning. And for replication we will drop sequence id while writing to peer cluster so in the slave we don't know what the order they are being written. If the pushing is disordered, the result will be wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)