[
https://issues.apache.org/jira/browse/HBASE-18626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416690#comment-16416690
]
Hudson commented on HBASE-18626:
--------------------------------
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Handle the incompatible change about the replication TableCFs' config
> ---------------------------------------------------------------------
>
> Key: HBASE-18626
> URL: https://issues.apache.org/jira/browse/HBASE-18626
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-3
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 1.4.0
>
> Attachments: HBASE-18626.branch-1.001.patch
>
>
> About compatibility, there is one incompatible change about the replication
> TableCFs' config. The old config is a string and it concatenate the list of
> tables and column families in format "table1:cf1,cf2;table2:cfA,cfB" in
> zookeeper for table-cf to replication peer mapping. When parse the config, it
> use ":" to split the string. If table name includes namespace, it will be
> wrong (See HBASE-11386). It is a problem since we support namespace (0.98).
> So HBASE-11393 (and HBASE-16653) changed it to a PB object. When rolling
> update cluster, you need rolling master first. And the master will try to
> translate the string config to a PB object. But there are two problems.
> 1. Permission problem. The replication client can write the zookeeper
> directly. So the znode may have different owner. And master may don't have
> the write permission for the znode. It maybe failed to translate old
> table-cfs string to new PB Object. See HBASE-16938
> 2. We usually keep compatibility between old client and new server. But the
> old replication client may write a string config to znode directly. Then the
> new server can't parse them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
