[
https://issues.apache.org/jira/browse/HBASE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099757#comment-13099757
]
stack commented on HBASE-2195:
------------------------------
You think we should expose this version Ted? I'd think it an internal
implementation detail. Hopefully, the case should be that the clients never
have to worry what version their HLogKey is. It always just works whatever
data format is thrown at it because internally it'll do the right thing
instantiating an HLogKey though given version 0 or version 1 data. It seems
like HLogKey does what VersionedWritable adds (but for the getVersion method)
> Support cyclic replication
> --------------------------
>
> Key: HBASE-2195
> URL: https://issues.apache.org/jira/browse/HBASE-2195
> Project: HBase
> Issue Type: Sub-task
> Components: replication
> Reporter: Jean-Daniel Cryans
> Assignee: Lars Hofhansl
> Attachments: 2195-v10.txt, 2195-v12.txt, 2195-v5.txt, 2195-v6.txt,
> 2195.txt
>
>
> We need to support cyclic replication by using the cluster id of each HlogKey
> and stop replicating when it goes back to the original cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
