You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2012/06/01 08:57:23 UTC
[jira] [Created] (HBASE-6146) Disabling of Catalog tables should
not be allowed
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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291037#comment-13291037 ]
ramkrishna.s.vasudevan commented on HBASE-6146:
-----------------------------------------------
+1 on this.
> 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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287350#comment-13287350 ]
Hadoop QA commented on HBASE-6146:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12530537/HBASE-6146_Trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.replication.TestReplication
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2082//testReport/
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2082//console
This message is automatically generated.
> 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
[jira] [Closed] (HBASE-6146) Disabling of Catalog tables should not
be allowed
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl closed HBASE-6146.
--------------------------------
> 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.94.1, 0.96.0
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291084#comment-13291084 ]
stack commented on HBASE-6146:
------------------------------
+1 Good one Anoop.
> 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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291425#comment-13291425 ]
Hudson commented on HBASE-6146:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #48 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/48/])
HBASE-6146 Disabling of Catalog tables should not be allowed (Anoop) (Revision 1347719)
Result = FAILURE
ramkrishna :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/trunk/hbase-server/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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291140#comment-13291140 ]
ramkrishna.s.vasudevan commented on HBASE-6146:
-----------------------------------------------
Will commit this patch.
> 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
[jira] [Updated] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ramkrishna.s.vasudevan updated HBASE-6146:
------------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk and 0.94
Thanks for the patch Anoop and to Stack for his review.
> 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
[jira] [Updated] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Anoop Sam John (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anoop Sam John updated HBASE-6146:
----------------------------------
Attachment: HBASE-6146_Trunk.patch
HBASE-6146_94.patch
Patches for 0.94 and Trunk
> 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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Anoop Sam John (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287373#comment-13287373 ]
Anoop Sam John commented on HBASE-6146:
---------------------------------------
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.replication.TestReplication
This seems not at all related to this patch
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
This is coming because of HBASE-6138
> 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
[jira] [Updated] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Anoop Sam John (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anoop Sam John updated HBASE-6146:
----------------------------------
Fix Version/s: 0.94.1
0.96.0
Status: Patch Available (was: Open)
> 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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291238#comment-13291238 ]
Hudson commented on HBASE-6146:
-------------------------------
Integrated in HBase-0.94 #251 (See [https://builds.apache.org/job/HBase-0.94/251/])
HBASE-6146 Disabling of Catalog tables should not be allowed (Anoop) (Revision 1347718)
Result = FAILURE
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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-6146) Disabling of Catalog tables should
not be allowed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291208#comment-13291208 ]
Hudson commented on HBASE-6146:
-------------------------------
Integrated in HBase-TRUNK #3000 (See [https://builds.apache.org/job/HBase-TRUNK/3000/])
HBASE-6146 Disabling of Catalog tables should not be allowed (Anoop) (Revision 1347719)
Result = FAILURE
ramkrishna :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* /hbase/trunk/hbase-server/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