Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 9 Jun 2017 08:54:18 +0000 (UTC)
From: "Yu Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12997255.1471252557000.37325.1496998458270@Atlassian.JIRA>
In-Reply-To: <JIRA.12997255.1471252557000@Atlassian.JIRA>
References: <JIRA.12997255.1471252557000@Atlassian.JIRA> <JIRA.12997255.1471252557081@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-16415) Replication in different namespace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 09 Jun 2017 08:54:23 -0000


    [ https://issues.apache.org/jira/browse/HBASE-16415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044168#comment-16044168 ] 

Yu Li commented on HBASE-16415:
-------------------------------

FWIW, taking usage of {{NamespaceGroupingStrategy}} introduced in HBASE-14456 together with multiwal may make the design simpler 

> Replication in different namespace
> ----------------------------------
>
>                 Key: HBASE-16415
>                 URL: https://issues.apache.org/jira/browse/HBASE-16415
>             Project: HBase
>          Issue Type: New Feature
>          Components: Replication
>            Reporter: Christian Guegi
>
> It would be nice to replicate tables from one namespace to another namespace.
> Example:
> Master cluster, namespace=default, table=bar
> Slave cluster, namespace=dr, table=bar
> Replication happens in class ReplicationSink:
>   public void replicateEntries(List<WALEntry> entries, final CellScanner cells, ...){
>     ...
>     TableName table = TableName.valueOf(entry.getKey().getTableName().toByteArray());
>     ...
>     addToHashMultiMap(rowMap, table, clusterIds, m);
>     ...
>     for (Entry<TableName, Map<List<UUID>, List<Row>>> entry : rowMap.entrySet()) {
>       batch(entry.getKey(), entry.getValue().values());
>     }
>    }


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)