[
https://issues.apache.org/jira/browse/HBASE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403319#comment-13403319
]
stack commented on HBASE-6239:
------------------------------
+1 on patch.
Pity this is so ugly:
{code}
+ HLog.Entry[] entries = new HLog.Entry[3];
+ long now = System.currentTimeMillis();
+ for(int i = 0; i < 3; i++) {
+ entries[i] = createEntry(TABLE_NAME1, 1, i, KeyValue.Type.Put, now+i);
+ }
+ // Kinda ugly, trying to merge all the entries into one
+ entries[0].getEdit().add(entries[1].getEdit().getKeyValues().get(0));
+ entries[0].getEdit().add(entries[2].getEdit().getKeyValues().get(0));
+ HLog.Entry[] entry = new HLog.Entry[1];
+ entry[0] = entries[0];
+ SINK.replicateEntries(entry);
{code}
...but its not a blocker. Commit. Backport to 0.94?
> [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: Critical
> 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
