[
https://issues.apache.org/jira/browse/HBASE-21857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765008#comment-16765008
]
Hudson commented on HBASE-21857:
--------------------------------
Results for branch branch-2.1
[build #854 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/854/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/854//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/854//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/854//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Do not need to check clusterKey if replicationEndpoint is provided when
> adding a peer
> -------------------------------------------------------------------------------------
>
> Key: HBASE-21857
> URL: https://issues.apache.org/jira/browse/HBASE-21857
> Project: HBase
> Issue Type: Improvement
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.3, 2.3.0
>
> Attachments: HBASE-21857-addendum.patch, HBASE-21857.patch
>
>
> The clusterKey check is done in HBASE-19630, which is part of the work for
> HBASE-19397.
> In HBASE-19630 we claim that we always check clusterKey when adding a peer at
> RS side, but this is not true, as clusterKey could be null. And it will be
> strange that if we implement a ReplicationEndpoint to kafka and we still need
> to provide a cluster key in the hbase format.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
