[
https://issues.apache.org/jira/browse/HBASE-16415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046157#comment-16046157
]
Guanghao Zhang commented on HBASE-16415:
----------------------------------------
Now the replication source read the wal entries by reader thread and filter wal
entries by the filter config (replication scope, perr table-cfs, peer
namespaces, etc.). Then ship them by shipper thread. They were write to peer
cluster by replication endpoint. And we already suppose the pluggable
replication endpoint. So I thought we should implement this feature
(replication in different namespace) by implementing a new replication
endpoint. And use the config now for replication endpoint. Your proposal will
make the replication source more complicate. IMO it is not a good idea.
> 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
> Assignee: Jan Kunigk
>
> 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)
