[
https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536698#comment-13536698
]
Hudson commented on HBASE-7158:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #304 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/304/])
HBASE-7158 Allow CopyTable to identify the source cluster (for replication
scenarios) (Revision 1424193)
Result = FAILURE
jdcryans :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/Mutation.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java
> Allow CopyTable to identify the source cluster (for replication scenarios)
> --------------------------------------------------------------------------
>
> Key: HBASE-7158
> URL: https://issues.apache.org/jira/browse/HBASE-7158
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Jean-Daniel Cryans
> Fix For: 0.96.0, 0.94.4
>
> Attachments: HBASE-7158-0.94-v1.patch
>
>
> When I worked on HBASE-2195 I added a mechanism for an edit to identify its
> source cluster, so that replication would not bounce it back to the source.
> See: {{this.clusterId =
> zkHelper.getUUIDForCluster(zkHelper.getZookeeperWatcher());}} in
> ReplicationSource, and {{put.setClusterId(entry.getKey().getClusterId());}}
> in ReplicationSink.
> In master-master replication scenarios, it would very useful if CopyTable
> would identify the source cluster (by tagging each Put/Delete with the source
> clusterId before applying it).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
