[
https://issues.apache.org/jira/browse/IMPALA-7917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787338#comment-16787338
]
ASF subversion and git services commented on IMPALA-7917:
---------------------------------------------------------
Commit b32ca155ea463187bdee87e74039d3dcd2681603 in impala's branch
refs/heads/master from Fredy Wijaya
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b32ca15 ]
IMPALA-7917 (Part 2): Decouple Sentry from Impala
This patch adds a new flag --authorization_factory_class and creates
some factories to make it easier to switch to a different authorization
provider. For backward compatability the default authorization provider
is still set to Sentry.
The --authorization_factory_class is used to specify which authorization
provider implementation to use.
This patch has no functional change.
Testing:
- Ran all FE tests
- Ran all authorization E2E tests
Change-Id: I051d06451fb14ba2ffb3f7e0d4aae37dee55ab86
Reviewed-on: http://gerrit.cloudera.org:8080/12542
Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> 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
>
> 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: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
