You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Zheng Hu (JIRA)" <ji...@apache.org> on 2017/09/15 02:23:02 UTC

[jira] [Updated] (HBASE-18822) Create table for peer cluster automatically when creating table in source cluster of using namespace replication.

     [ https://issues.apache.org/jira/browse/HBASE-18822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zheng Hu updated HBASE-18822:
-----------------------------
    Description: 
In our cluster of using namespace replication,   we always forget to create table in peer cluster, which lead to replication get stuck. 

We have implemented the feature in our cluster:  create table for peer cluster automatically when creating table in source cluster of using namespace replication.
 
I'm not sure if someone else needs this feature, so create an issue here for discussing   
        Summary: Create table for peer cluster automatically when creating table in source cluster of using namespace replication.  (was: create table for peer cluster automatically when creating table in source cluster of using namespace replication.)

> Create table for peer cluster automatically when creating table in source cluster of using namespace replication.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18822
>                 URL: https://issues.apache.org/jira/browse/HBASE-18822
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 2.0.0-alpha-2
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>
> In our cluster of using namespace replication,   we always forget to create table in peer cluster, which lead to replication get stuck. 
> We have implemented the feature in our cluster:  create table for peer cluster automatically when creating table in source cluster of using namespace replication.
>  
> I'm not sure if someone else needs this feature, so create an issue here for discussing   



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)