You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2012/06/01 09:01:24 UTC
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287212#comment-13287212 ]
ramkrishna.s.vasudevan commented on HBASE-6146:
-----------------------------------------------
We can just add a check in the first line of disable and enable api to see if the table name is a CATALOG table. If so just throw error.
> 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