[
https://issues.apache.org/jira/browse/HBASE-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295521#comment-14295521
]
Matteo Bertozzi commented on HBASE-11869:
-----------------------------------------
[~ndimiduk] +1 for me, what Enis mentioned above was more a "design" concern,
and it applies to this patch and not to a specific branch.
I've no strong opinion. Having the owner embedded in the manifest is the easy
way to have some kind of security (which is more granular than "only the admin
can do that"), and the code changes are almost none. Having the same logic as
ACLs for table will be probably more code, but as Enis mentioned it will allow
more flexibility (e.g. adding/removing "owner" at runtime or similar)
> Support snapshot owner
> ----------------------
>
> Key: HBASE-11869
> URL: https://issues.apache.org/jira/browse/HBASE-11869
> Project: HBase
> Issue Type: Improvement
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-11869-1.0-v1.diff, HBASE-11869-trunk-v1.diff,
> HBASE-11869-trunk-v3.diff, HBASE-11869-trunk-v4.diff
>
>
> In current codebase, the table snapshot operations only can be done by the
> global admin , not by the table admin.
> There is a multi-tenant hbase cluster, each table has different snapshot
> policies, eg: do snapshot per week, or snapshot after the new data are
> imported.
> We want to release the snapshot permission to each table admin.
> According to [~mbertozzi]'s suggestion, we implement the snapshot owner
> feature.
> * The user with table admin permission can create snapshot and the owner of
> this snapshot is this user.
> * The owner of snapshot can delete and restore the snapshot.
> * Only the user with global admin permission can clone a snapshot, for this
> operation creates a new table.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
