[
https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400014#comment-13400014
]
Hudson commented on HBASE-6146:
-------------------------------
Integrated in HBase-0.94-security #37 (See
[https://builds.apache.org/job/HBase-0.94-security/37/])
HBASE-6146 Disabling of Catalog tables should not be allowed (Anoop)
(Revision 1347718)
Result = SUCCESS
ramkrishna :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java
> 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
> Fix For: 0.96.0, 0.94.1
>
> Attachments: HBASE-6146_94.patch, HBASE-6146_Trunk.patch
>
>
> 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
