[
https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438520#comment-15438520
]
Sai Teja Ranuva commented on HBASE-16504:
-----------------------------------------
Thanks Phil, I think everything makes more sense to me now.
For the case of replication, the cells will already have a timestamp set, so
the put timestamp is of no use.
> Replication is not preserving the timestamp of the cell
> -------------------------------------------------------
>
> Key: HBASE-16504
> URL: https://issues.apache.org/jira/browse/HBASE-16504
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Sai Teja Ranuva
> Priority: Minor
> Labels: replication, replication-testing
>
> The Replication procedure in ReplicationSink.replicateEntries() method is not
> preserving the timestamp of the cell.
> Pointer to the code:
> m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(),
> cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(),
> cell.getRowOffset(),cell.getRowLength());
> The Put and Delete constructors called here assign the timestamp with
> HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the
> cell here.
> Also there doesn't seem to be a test which checks if replication is
> preserving the timestamp.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
