You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Benoit Sigoure (JIRA)" <ji...@apache.org> on 2012/06/22 18:26:43 UTC
[jira] [Commented] (HBASE-6239) [replication] ReplicationSink uses
the ts of the first KV for the other KVs in the same row
[ https://issues.apache.org/jira/browse/HBASE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399417#comment-13399417 ]
Benoit Sigoure commented on HBASE-6239:
---------------------------------------
I would argue that this bug is not "minor", because we're talking about data being corrupted by HBase.
> [replication] ReplicationSink uses the ts of the first KV for the other KVs in the same row
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-6239
> URL: https://issues.apache.org/jira/browse/HBASE-6239
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.6, 0.92.1
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Minor
> Labels: corruption
> Fix For: 0.92.2
>
> Attachments: HBASE-6239-0.92-v1.patch
>
>
> ReplicationSink assumes that all the KVs for the same row inside a WALEdit will have the same timestamp, which is not necessarily the case.
> This only affects 0.90 and 0.92 since HBASE-5203 fixes it in 0.94
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira