[
https://issues.apache.org/jira/browse/IMPALA-12921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fang-Yu Rao updated IMPALA-12921:
---------------------------------
Description:
It would be nice to be able to support locally built Ranger in Impala's
minicluster in that it would facilitate the testing of features that require
changes to both components.
*+Edit:+*
Making the current Apache Impala on *master* (tip is
{*}IMPALA-12925{*}: Fix decimal data type for external JDBC table) to support
Ranger on *master* (tip is
{*}RANGER-4745{*}: Enhance handling of subAccess authorization in Ranger HDFS
plugin) may be too ambitious.
The signatures of some classes are already incompatible. For instance, on the
Impala side, Impala instantiates the instance of *RangerAccessRequestImpl* via
the following code. 4 input arguments are needed.
{code:java}
RangerAccessRequest req = new RangerAccessRequestImpl(resource,
SELECT_ACCESS_TYPE, user.getShortName(), getUserGroups(user));
{code}
However, the current signature of RangerAccessRequestImpl's constructor on the
master of Apache Ranger is the following. It can be seen we need 5 input
arguments instead.
{code:java}
public RangerAccessRequestImpl(RangerAccessResource resource, String
accessType, String user, Set<String> userGroups, Set<String> userRoles)
{code}
It may be more practical to support Ranger on an earlier version, e.g.,
[https://github.com/apache/ranger/blob/release-ranger-2.4.0].
was:It would be nice to be able to support locally built Ranger in Impala's
minicluster in that it would facilitate the testing of features that require
changes to both components.
> Consider adding support for locally built Ranger
> ------------------------------------------------
>
> Key: IMPALA-12921
> URL: https://issues.apache.org/jira/browse/IMPALA-12921
> Project: IMPALA
> Issue Type: Task
> Reporter: Fang-Yu Rao
> Assignee: Fang-Yu Rao
> Priority: Major
>
> It would be nice to be able to support locally built Ranger in Impala's
> minicluster in that it would facilitate the testing of features that require
> changes to both components.
> *+Edit:+*
> Making the current Apache Impala on *master* (tip is
> {*}IMPALA-12925{*}: Fix decimal data type for external JDBC table) to support
> Ranger on *master* (tip is
> {*}RANGER-4745{*}: Enhance handling of subAccess authorization in Ranger HDFS
> plugin) may be too ambitious.
> The signatures of some classes are already incompatible. For instance, on the
> Impala side, Impala instantiates the instance of *RangerAccessRequestImpl*
> via the following code. 4 input arguments are needed.
> {code:java}
> RangerAccessRequest req = new RangerAccessRequestImpl(resource,
> SELECT_ACCESS_TYPE, user.getShortName(), getUserGroups(user));
> {code}
> However, the current signature of RangerAccessRequestImpl's constructor on
> the master of Apache Ranger is the following. It can be seen we need 5 input
> arguments instead.
> {code:java}
> public RangerAccessRequestImpl(RangerAccessResource resource, String
> accessType, String user, Set<String> userGroups, Set<String> userRoles)
> {code}
> It may be more practical to support Ranger on an earlier version, e.g.,
> [https://github.com/apache/ranger/blob/release-ranger-2.4.0].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
