[
https://issues.apache.org/jira/browse/HBASE-12947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299020#comment-14299020
]
Andrew Purtell commented on HBASE-12947:
----------------------------------------
bq. When tables are created dynamically in Hbase cluster, the Replication
feature can't be used as the new table does not exist in peer cluster. To use
the replication, we need to create same table in peer cluster also.
This has been by design up to now because auto-synchronizing schema updates
among multiple sites is a challenging problem, and more so in the presence of
cyclical relationships, as you mention. Aside from technical concerns there are
also policy considerations.
I like this proposal in that propagation of schema changes to other sites is
optional, it must be enabled with a flag. In addition there should be strong
security and/or configuration barriers to accidental schema propagation
because, as a multi-site operator, I don't want unauthorized or ill-advised
changes at one site automatically propagating to others.
> Replicating DDL statements like create from one cluster to another
> -------------------------------------------------------------------
>
> Key: HBASE-12947
> URL: https://issues.apache.org/jira/browse/HBASE-12947
> Project: HBase
> Issue Type: New Feature
> Components: Replication
> Affects Versions: 2.0.0
> Reporter: Prabhu Joseph
> Priority: Critical
> Fix For: 2.0.0
>
>
> Problem:
> When tables are created dynamically in Hbase cluster, the Replication
> feature can't be used as the new table does not exist in peer cluster. To use
> the replication, we need to create same table in peer cluster also.
> Having API to replicate the create table statement at peer cluster will be
> more helpful in such cases.
> Solution:
> create 'table','cf',replication => true , peerFlag => true
> if peerFlag = true, the table with the column family has to be created at
> peer
> cluster.
> Special cases like enabling replication at peer cluster also for cyclic
> replication has to be considered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
