[
https://issues.apache.org/jira/browse/HBASE-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914759#comment-13914759
]
Alex Nastetsky commented on HBASE-9206:
---------------------------------------
Hi, is this ticket still being worked on? There hasn't been any activity since
October.
Currently, any user can either drop anyone else's table OR that user can not
create their own tables, which presents a problem. It looks like this ticket
would provide the ability to both have separate permissions in different
namespaces, as well as separating the permissions for creating and
deleting/dropping tables.
> namespace permissions
> ---------------------
>
> Key: HBASE-9206
> URL: https://issues.apache.org/jira/browse/HBASE-9206
> Project: HBase
> Issue Type: Sub-task
> Reporter: Francis Liu
>
> Now that we have namespaces let's address how we can give admins more
> flexibility.
> Let's list out the privileges we'd like. Then we can map it to existing
> privileges and see if we need more.
> So far we have:
> 1. Modify namespace descriptor (ie quota, other values)
> 2. create namespace
> 3. delete namespace
> 4. list tables in namespace
> 5. create/drop tables in a namespace
> 6. All namespace's tables create
> 7. All namespace's tables write
> 8. All namespace's tables execute
> 9. All namespace's tables delete
> 10. All namespace's tables admin
> 1-3, is currently set to global admin only. Which seems acceptable to me.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
