Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 1 Jun 2012 06:57:23 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1574379615.25609.1338533843346.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (HBASE-6146) Disabling of Catalog tables should
 not be allowed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Anoop Sam John created HBASE-6146:
-------------------------------------

             Summary: Disabling of Catalog tables should not be allowed
                 Key: HBASE-6146
                 URL: https://issues.apache.org/jira/browse/HBASE-6146
             Project: HBase
          Issue Type: Bug
          Components: client
            Reporter: Anoop Sam John
            Assignee: Anoop Sam John


HBaseAdmin#disableTable() when called with META or ROOT table, it will pass the disable instruction to Master and table is actually getting disabled. Later this API call will fail as there is a call to HBaseAdmin#isTableDisabled() which is having a check like isLegalTableName(tableName).So this call makes the catalog table to be in disabled state.

We can have same kind of isLegalTableName(tableName) checks in disableTable() and enableTable() APIs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira