[
https://issues.apache.org/jira/browse/IMPALA-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16828785#comment-16828785
]
ASF subversion and git services commented on IMPALA-8309:
---------------------------------------------------------
Commit 42e326244857b3b03a659b34fd038f9036dddbe3 in impala's branch
refs/heads/master from Radford Nguyen
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=42e3262 ]
IMPALA-8309: add user authorization_provider flag
This commit adds a `authorization_provider` user-facing flag
in order to provide a more human-readable alternative to the
`authorization_factory_class` for internally-provided
authorization strategies.
The `authorization_factory_class` flag is retained, but no
longer takes a default value if not specified. The default
for `authorization_provider` is "sentry" in order to retain
backwards-compatibility.
If specified, `authorization_factory_class` will take
precedence.
Testing:
- Manually started minicluster with each of following flags
and verified correct authorization strategy chosen:
- provider='' factory='' => sentry
- provider=sentry factory='' => sentry
- provider=ranger factory='' => ranger
- provider='' factory=sentry => sentry
- provider='' factory=ranger => ranger
- provider=sentry factory=sentry => sentry
- provider=ranger factory=sentry => sentry
- provider=sentry factory=ranger => ranger
- provider=ranger factory=ranger => ranger
- Wrote unit tests to capture above assertions
- Ran fe unit and e2e tests
- Wrote e2e test to verify new flag behavior
Change-Id: I001c20505ba4f0562b60fdef73d15308e8500c19
Reviewed-on: http://gerrit.cloudera.org:8080/12901
Reviewed-by: Fredy Wijaya <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Use a more human-readable flag to switch to a different authorization provider
> ------------------------------------------------------------------------------
>
> Key: IMPALA-8309
> URL: https://issues.apache.org/jira/browse/IMPALA-8309
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Fredy Wijaya
> Assignee: radford nguyen
> Priority: Critical
>
> We currently use authorization_factory_class flag to switch to a different
> authorization provider, which is useful for any third party to provide an
> implementation of authorization provider. Since, Sentry and Ranger are
> officially supported by Impala, we should have a flag, i.e.
> authorization_provider=[sentry|ranger] to easily switch between officially
> supported authorization providers.
> At the time of this writing, the existing {{authorization_factory_class}}
> flag is being retained but its default value removed. If present, it will
> take precedence over the {{authorization_provider}} flag being added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
