[jira] [Resolved] (IMPALA-12985) Use the new constructor when instantiating RangerAccessRequestImpl

["Fang-Yu Rao (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-12985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fang-Yu Rao resolved IMPALA-12985.
----------------------------------
    Resolution: Fixed

Resolve the issue since the fix has been merged.

> Use the new constructor when instantiating RangerAccessRequestImpl
> ------------------------------------------------------------------
>
>                 Key: IMPALA-12985
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12985
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>            Reporter: Fang-Yu Rao
>            Assignee: Fang-Yu Rao
>            Priority: Major
>             Fix For: Impala 4.5.0
>
>
> After RANGER-2763, we changed the signature of the class RangerAccessRequestImpl in by adding an additional input argument 'userRoles' as shown in the following.
> {code:java}
> public RangerAccessRequestImpl(RangerAccessResource resource, String accessType, String user, Set<String> userGroups, Set<String> userRoles) {
> ...
> {code}
> The new signature is also provided in CDP Ranger. Thus to unblock IMPALA-12921 or to be able to build Apache Impala with locally built Apache Ranger, it may be faster to switch to the new signature on the Impala side than waiting for RANGER-4770 to be resolved on the Ranger side.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)