[
https://issues.apache.org/jira/browse/KUDU-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167169#comment-17167169
]
ASF subversion and git services commented on KUDU-3090:
-------------------------------------------------------
Commit 4bed2723490135dc1afa2a609f9d56fc6e82098a in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=4bed272 ]
KUDU-3090 Allow restoring tables without owner
fad779cf7 introduced backing up and restoring table ownership as part of
the backup tool. 6f0e858ba restricted changing ownership to users with
ALL + delegate admin privileges which is higher than what we required
for running restore. To support running the restore job without having
to grant additional privileges, this commit adds a new "restoreOwner"
flag to the restore job which is true by default, but if set to false,
the job creates tables as the logged in user which still requires the
same privileges as before.
Change-Id: I22d0b78858f60fafd3c116c7e4b3371839440d6c
Reviewed-on: http://gerrit.cloudera.org:8080/16239
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Reviewed-by: Grant Henke <granthe...@apache.org>
> Add owner concept in Kudu
> -------------------------
>
> Key: KUDU-3090
> URL: https://issues.apache.org/jira/browse/KUDU-3090
> Project: Kudu
> Issue Type: New Feature
> Components: authz, security
> Reporter: Hao Hao
> Assignee: Attila Bukor
> Priority: Major
> Labels: roadmap-candidate
>
> As mentioned in the Ranger integration design doc, Ranger supports ownership
> privilege by creating a default policy that allows \{OWNER} of a resource to
> access it without creating additional policy manually. Unless Kudu actually
> has a full support for owner, ownership privilege is not possible with Ranger
> integration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
