Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 42E95DC8E for ; Thu, 20 Dec 2012 02:27:14 +0000 (UTC) Received: (qmail 99065 invoked by uid 500); 20 Dec 2012 02:27:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 99023 invoked by uid 500); 20 Dec 2012 02:27:14 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 99014 invoked by uid 99); 20 Dec 2012 02:27:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 02:27:14 +0000 Date: Thu, 20 Dec 2012 02:27:13 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-7158) Allow CopyTable to identify the source cluster (for replication scenarios) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536709#comment-13536709 ] Hudson commented on HBASE-7158: ------------------------------- Integrated in HBase-0.94 #647 (See [https://builds.apache.org/job/HBase-0.94/647/]) Missing imports for HBASE-7158 (Revision 1424229) HBASE-7158 Allow CopyTable to identify the source cluster (for replication scenarios) (Revision 1424192) Result = FAILURE jdcryans : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java jdcryans : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/Mutation.java * /hbase/branches/0.94/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