[
https://issues.apache.org/jira/browse/HBASE-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020205#comment-15020205
]
Enis Soztutar commented on HBASE-11393:
---------------------------------------
bq. Why not forbidden user to update tableCF zNode directly during roll
upgrading? It will be more simple and clear. wdyt
There is no easy and reliable way to detect a rolling upgrade going on and
whether it is finished, etc. Since adding tables with NS to tableCFs is already
broken now, it should be fine that it is not fixed until you have this patch
working in all your regionservers via rolling upgrade before you add such a
table.
> Replication TableCfs should be a PB object rather than a string
> ---------------------------------------------------------------
>
> Key: HBASE-11393
> URL: https://issues.apache.org/jira/browse/HBASE-11393
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Fix For: 2.0.0
>
> Attachments: HBASE-11393.patch, HBASE-11393_v1.patch,
> HBASE-11393_v10.patch, HBASE-11393_v2.patch, HBASE-11393_v3.patch,
> HBASE-11393_v4.patch, HBASE-11393_v5.patch, HBASE-11393_v6.patch,
> HBASE-11393_v7.patch, HBASE-11393_v8.patch, HBASE-11393_v9.patch
>
>
> We 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.
> This results in ugly parsing code. We should do this a PB object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
