[
https://issues.apache.org/jira/browse/HBASE-19293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258726#comment-16258726
]
Duo Zhang commented on HBASE-19293:
-----------------------------------
And yes, add default modifier for the new methods introduced in 2.0 may benefit
users who implement their own Admin, but I'm still neutral on this. We should
depend on the method itself to decide whether to make it default. If it is a
critical method that must be presented then it should not be declared as
default method, even if it may break the compatibility. I believe we already
mentioned this in our ref guide.
I'm not familiar with the background of the replication related methods in
Admin, seems they are moved from ReplicationAdmin? [~zghaobac] Why we add the
default modifier at beginning but then remove them in this patch?
Thanks.
> Support add a disabled state replication peer directly
> ------------------------------------------------------
>
> Key: HBASE-19293
> URL: https://issues.apache.org/jira/browse/HBASE-19293
> Project: HBase
> Issue Type: Improvement
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19293.master.001.patch,
> HBASE-19293.master.002.patch
>
>
> Now when add a replication peer, the default state is enabled. If you want
> add a disabled replication peer, you need add a peer first, then disable it.
> It need two step to finish now.
> Use case for add a disabled replication peer. When user want sync data from a
> cluster A to a new peer cluster.
> 1. Add a disabled replication peer. And config the table to peer config.
> 2. Take a snapshot of table and export snapshot to peer cluster.
> 3. Restore snapshot in peer cluster.
> 4. Enable the peer and wait all stuck replication log replicated to peer
> cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
