[
https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439481#comment-15439481
]
Sai Teja Ranuva commented on HBASE-16504:
-----------------------------------------
By preserving the timestamp, I meant the put timestamp during replication.
But it looks like it is not used/useful anywhere.
There is already a check for the cell timestamps(i.e complete replicated cell
is matched, so all dimensions are taken care).
If we plan to carry forward the put timestamp during replication too, then we
need to add a test case to check it.
> 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
> Assignee: Sai Teja Ranuva
> Priority: Minor
> Labels: question, replication
>
> 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)
