[
https://issues.apache.org/jira/browse/KUDU-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051785#comment-17051785
]
ASF subversion and git services commented on KUDU-2972:
-------------------------------------------------------
Commit e13fd4a489bb252ae80f1a2d8dd39991cfdc2a88 in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e13fd4a ]
KUDU-2972 Add Ranger client
Adds a Ranger client that communicates with the Java subprocess that
wraps the Ranger plugin. It can be used by an authorization provider to
translate between Kudu and Ranger.
Removes default_database out parameter from ParseRangerTableIdentifier
in table_util as we decided to take a slightly different path and this
information is not needed anymore.
Current test coverage consists of only unit tests with a mock subprocess
server. Real integration tests will be added in a follow-up patch once a
working MiniRanger is added to facilitate this testing.
Change-Id: Ie2e1ec19ed3aeb4d82ad38fe1fb655f57021c1a4
Reviewed-on: http://gerrit.cloudera.org:8080/15206
Reviewed-by: Hao Hao <[email protected]>
Tested-by: Andrew Wong <[email protected]>
> Add Ranger authorization provider
> ---------------------------------
>
> Key: KUDU-2972
> URL: https://issues.apache.org/jira/browse/KUDU-2972
> Project: Kudu
> Issue Type: Sub-task
> Affects Versions: 1.11.0
> Reporter: Hao Hao
> Assignee: Attila Bukor
> Priority: Major
>
> For Ranger integration, we need to create Ranger authorization provider to
> retrieve authorization decisions from the wrapped Ranger plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
