[ 
https://issues.apache.org/jira/browse/IMPALA-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581786#comment-16581786
 ] 

ASF subversion and git services commented on IMPALA-7075:
---------------------------------------------------------

Commit a23e6f296369854b7fade98bf476242c1201dacc in impala's branch 
refs/heads/master from [~fredyw]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=a23e6f2 ]

IMPALA-7342: Add initial support for user-level permissions

This patch refactors the authorization code in preparation to add initial
support for for user-level permissions (IMPALA-6794) and object ownership
(IMPALA-7075). It introduces the notion of Principal that can be either
Role or User. The authorization tests are updated to run the tests with
user and role permissions.

Testing:
- Update authorization tests
- Ran core tests

Change-Id: I07e0d46d2e50d35bd64ee573b5aa4b779eb9e62f
Reviewed-on: http://gerrit.cloudera.org:8080/11039
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Add support for object ownership for Impala
> -------------------------------------------
>
>                 Key: IMPALA-7075
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7075
>             Project: IMPALA
>          Issue Type: Epic
>          Components: Frontend
>            Reporter: Fredy Wijaya
>            Assignee: Fredy Wijaya
>            Priority: Major
>              Labels: security
>
> Currently when creating a database or table, a user does not automatically 
> get ALL privilege on that object even though that person owns the 
> table/object. The purpose of this epic is to add a concept of ownership where 
> a user will automatically be granted ALL on the database/table he/she owns.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to