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

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

Commit 3135af8c437b3756da57a5d31d9e4080da07ec02 in impala's branch 
refs/heads/master from Fredy Wijaya
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=3135af8 ]

IMPALA-7917 (Part 3): Decouple Sentry from Impala

The third part of this patch introduces an interface called
AuthorizationManager to perform authorization management related
functions, such as granting/revoking a privilege, etc. Some existing
authorization management methods have been refactored to reduce the
need for if/else conditions to perform certain actions. This patch
moves code related to Sentry authorization management code to:
- SentryCatalogdAuthorizationManager
- SentryImpaladAuthorizationManager
The split makes it easier to differentiate between authorization DDL
operations performed in Catalogd vs Impalad.

This patch does not implement AuthorizationManager for Ranger.

This patch has no functionality change.

Testing:
- Ran all FE tests
- Ran all E2E authorization tests

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


> Decouple Sentry from Impala
> ---------------------------
>
>                 Key: IMPALA-7917
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7917
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Catalog, Frontend
>            Reporter: Fredy Wijaya
>            Assignee: Fredy Wijaya
>            Priority: Major
>             Fix For: Impala 3.3.0
>
>
> The task will will involve decoupling Sentry from Impala, such as moving 
> Sentry specific code to a separate package/module and provide interfaces that 
> allows the flexibility to switch to a different authorization provider.



--
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