[
https://issues.apache.org/jira/browse/KUDU-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167170#comment-17167170
]
ASF subversion and git services commented on KUDU-3090:
-------------------------------------------------------
Commit b8826dfa7caa552c733e013b276cd1e03e3f33d1 in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=b8826df ]
[docs] KUDU-3090 Document table ownership
Change-Id: I331716a90667a90d5bf70ec837a80ea00be2f5d3
Reviewed-on: http://gerrit.cloudera.org:8080/16233
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <[email protected]>
Reviewed-by: Grant Henke <[email protected]>
Reviewed-by: Liliana Kadar <[email protected]>
> 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)
