[
https://issues.apache.org/jira/browse/HBASE-16447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-16447:
-----------------------------------
Release Note:
Support replication by namespaces config in peer.
1. Set a namespace in peer config means that all tables in this namespace will
be replicated.
2. If the namespaces config is null, then the table-cfs config decide which
table's edit can be replicated. If the table-cfs config is null, then the
namespaces config decide which table's edit can be replicated.
3. If you already have set a namespace in the peer config, then you can't set
any table of this namespace to the peer config. If you already have set a table
in the peer config, then you can't set this table's namespace to the peer
config.
was:
Support replication by namespaces config.
1. Config a namespace in peer means that all tables in this namespace will be
replicated.
2. If the peer didn't config any namespaces, then table-cfs config only decide
which table's edit can be replicated.
3. If the peer config a namespace, then the peer can't config any table of this
namespace. If the peer config a table, then the peer can't config this table's
namespace too.
> Replication by namespaces config in peer
> ----------------------------------------
>
> Key: HBASE-16447
> URL: https://issues.apache.org/jira/browse/HBASE-16447
> Project: HBase
> Issue Type: New Feature
> Components: Replication
> Affects Versions: 2.0.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Attachments: HBASE-16447-v1.patch
>
>
> Now we only config table cfs in peer. But in our production cluster, there
> are a dozen of namespace and every namespace has dozens of tables. It was
> complicated to config all table cfs in peer. For some namespace, it need
> replication all tables to other slave cluster. It will be easy to config if
> we support replication by namespace. Suggestions and discussions are welcomed.
> Review board: https://reviews.apache.org/r/51521/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
