hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17934) Backport HBASE-17779 "disable_table_replication returns misleading message and does not turn off replication" to branch-1.3
Date Sat, 09 Sep 2017 21:28:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Yu updated HBASE-17934:
---------------------------
    Status: Patch Available  (was: Open)

> Backport HBASE-17779 "disable_table_replication returns misleading message and does not
turn off replication" to branch-1.3
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17934
>                 URL: https://issues.apache.org/jira/browse/HBASE-17934
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Janos Gub
>             Fix For: 1.3.2
>
>         Attachments: 17934-branch-1.3.patch, HBASE-17934.patch
>
>
> Currently HBaseAdmin#isTableRepEnabled() returns false if ANY of the columns families
is not replicated.
> Because of this if you have a table where replication is partially enabled, calling disable_table_replication
will not have any effect, but will report that replication for a given table is disabled.
> Workaround is enabling table replication before disabling.
> As a solution quoted from HBASE-17460:
> Admin#disableTableReplication() returns nothing and isTableRepEnabled() returns boolean.
For master branch, we can let isTableRepEnabled() return enum (partially disabled, disabled,
etc) This way, Admin#disableTableReplication() can return meaningful value to the user.
> This issue is to backport the fix to branch-1.3



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message