You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2016/08/08 23:33:20 UTC
[jira] [Commented] (HBASE-12947) Replicating DDL statements like
create from one cluster to another
[ https://issues.apache.org/jira/browse/HBASE-12947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412646#comment-15412646 ]
Esteban Gutierrez commented on HBASE-12947:
-------------------------------------------
I ran across this recently and I concur with [~apurtell] on the the challenges. For instance, sometimes you would like to have the tables in the sink cluster using a different compression codec or a larger TTL than the source or depending on the namespace the users on the remote cluster might have some restriction on the use of coprocessors. I think tooling like {{bin/replication/copy_tables_desc.rb}} is ok for basic management, but for fine grain control we should revisit this as part of HBASE-14379.
> 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)