[
https://issues.apache.org/jira/browse/HBASE-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534445#comment-13534445
]
Andrew Purtell edited comment on HBASE-7367 at 12/18/12 12:05 AM:
------------------------------------------------------------------
bq. I'm a GLOBAL ADMIN, I create a table. The table is enabled by default
(every one can now write on it) meanwhile I set the permission... (too late
someone has already polluted the table)
Unless you grant access to this table, nobody but you as creator or ADMINs can
write on it.
They can't read it either.
was (Author: apurtell):
bq. I'm a GLOBAL ADMIN, I create a table. The table is enabled by default
(every one can now write on it) meanwhile I set the permission... (too late
someone has already polluted the table)
Unless you grant access to this table, nobody but you as creator or ADMINs can
write on it.
> Snapshot coprocessor and ACL security
> -------------------------------------
>
> Key: HBASE-7367
> URL: https://issues.apache.org/jira/browse/HBASE-7367
> Project: HBase
> Issue Type: Sub-task
> Components: Client, master, regionserver, snapshots, Zookeeper
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: hbase-6055, 0.96.0
>
> Attachments: HBASE-7367-v0.patch
>
>
> Currently snapshot don't care about ACL...
> and in the first draft snapshots should be disabled if the ACL coprocessor is
> enabled.
> After the first step, we can discuss how to handle the snapshot/restore/clone.
> Is saving and restoring the _acl_ related rights, the right way? maybe after
> 3 months we don't want to give the access the guys listed in the old _acl_...
--
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
