[
https://issues.apache.org/jira/browse/HBASE-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481059#comment-14481059
]
Anoop Sam John commented on HBASE-10619:
----------------------------------------
Sorry for the delay in rework on the patch. I some how missed this completely.
As per the comment from Andy, added the super user check. The super user can
create table in system namespace as well as disable tables in namespace. For
non super users these are not allowed.
Please note that for disable table, there is an extra check for META table.
Even for super user this op is not allowed. (This is what we were doing till
now). This is because for a disable op to complete, the META table should be
available. On disable request, we call the async op of DisableTableHandler.
The calles checks for all regions of that table to be in disabled state in
META. But for that META has to be up. Means we can not allow disable of META
even for super users.
> Don't allow non super users to disable/drop system tables
> ---------------------------------------------------------
>
> Key: HBASE-10619
> URL: https://issues.apache.org/jira/browse/HBASE-10619
> Project: HBase
> Issue Type: Bug
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Attachments: HBASE-10619.patch, HBASE-10619_V2.patch,
> HBASE-10619_V3.patch, HBASE-10619_V4.patch
>
>
> We should treat NS table just like META table, which is having checks so that
> user can not disable/drop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
