[
https://issues.apache.org/jira/browse/HBASE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099747#comment-13099747
]
Ted Yu edited comment on HBASE-2195 at 9/8/11 4:09 AM:
-------------------------------------------------------
At this moment, we're not using getVersion() of VersionedWritable. But there
might be future need for this method.
Here is an example from ThriftServer.getTableRegions() that uses
HRI.getVersion():
{code}
region.name = ByteBuffer.wrap(regionInfo.getRegionName());
region.version = regionInfo.getVersion();
regions.add(region);
{code}
This JIRA is targeting multi-cluster replication where we should expect
different releases of HBase to be in use. Providing HLogKey.getVersion() has
its benefits.
My two cents.
was (Author: yuzhih...@gmail.com):
At this moment, we're not using getVersion() of VersionedWritable. But
there might be future need for this method.
Here is an example from ThriftServer.getTableRegions() that uses
HRI.getVersion():
{code}
region.name = ByteBuffer.wrap(regionInfo.getRegionName());
region.version = regionInfo.getVersion();
regions.add(region);
{code}
In HRegionInfo, none of the methods from VersionedWritable is used.
This JIRA is targeting multi-cluster replication where we should expect
different releases of HBase to be in use. Providing HLogKey.getVersion() has
its benefits.
My two cents.
> 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
