You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2016/11/01 01:04:58 UTC

[jira] [Commented] (HBASE-16653) Backport HBASE-11393 to all branches which support namespace

    [ https://issues.apache.org/jira/browse/HBASE-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623953#comment-15623953 ] 

Guanghao Zhang commented on HBASE-16653:
----------------------------------------

Not a issue. You can create a peer without table-cfs config when rolling upgrade.

> Backport HBASE-11393 to all branches which support namespace
> ------------------------------------------------------------
>
>                 Key: HBASE-16653
>                 URL: https://issues.apache.org/jira/browse/HBASE-16653
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.4.0, 1.0.5, 1.3.1, 0.98.22, 1.1.7, 1.2.4
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>             Fix For: 1.4.0
>
>         Attachments: HBASE-16653-branch-1-v1.patch, HBASE-16653-branch-1-v2.patch, HBASE-16653-branch-1-v3.patch, HBASE-16653-branch-1-v4.patch, HBASE-16653-branch-1-v4.patch, HBASE-16653-branch-1-v5.patch
>
>
> As HBASE-11386 mentioned, the parse code about replication table-cfs config will be wrong when table name contains namespace and we can only config the default namespace's tables in the peer. It is a bug for all branches which support namespace. HBASE-11393 resolved this by use a pb object but it was only merged to master branch. Other branches still have this problem. I thought we should fix this bug in all branches which support namespace.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)