hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17112) Prevent setting timestamp of delta operations being same as previous value's
Date Wed, 16 Nov 2016 16:58:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670976#comment-15670976

Anoop Sam John commented on HBASE-17112:

For append/increment we will use TS as the RS cur time only? I mean even if client passed
any TS we will ignore those? A quick read of code gives such an impression?  Missing some

> 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
>    Affects Versions: 1.1.7, 0.98.23, 1.2.4
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>         Attachments: HBASE-17112-v1.patch
> 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

View raw message