[
https://issues.apache.org/jira/browse/HBASE-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-17112:
------------------------------
Description:
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.
We can set the new ts to previous+1 if the previous is not less than now.
was:
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.
> 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.
> We can set the new ts to previous+1 if the previous is not less than now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
