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

Xu Cang commented on HBASE-18822:
---------------------------------

[~openinx] thanks for showing this patch.

One question, seems like this patch makes the best effort to sync tables but 
does not guarantee all synced. Especially when I read 
#syncSchemaModificationToPeer, I realize it only modifies table when cf count 
is different. So there are still some work users need to do to verify/make sure 
table schema is synced.  

> 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
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: HBASE-18822.v1.patch, HBASE-18822.v1.patch
>
>
> 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
(v7.6.3#76005)

Reply via email to