You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Velmurugan Periasamy (Jira)" <ji...@apache.org> on 2024/04/16 21:38:00 UTC

[jira] [Assigned] (RANGER-4770) Make RangerAccessRequestImpl backward compatible after RANGER-2763

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

Velmurugan Periasamy reassigned RANGER-4770:
--------------------------------------------

    Assignee: Peter Turcsanyi

> Make RangerAccessRequestImpl backward compatible after RANGER-2763
> ------------------------------------------------------------------
>
>                 Key: RANGER-4770
>                 URL: https://issues.apache.org/jira/browse/RANGER-4770
>             Project: Ranger
>          Issue Type: Task
>          Components: admin
>            Reporter: Fang-Yu Rao
>            Assignee: Peter Turcsanyi
>            Priority: Major
>
> We changed the signature of the class RangerAccessRequestImpl in RANGER-2763 by adding an additional input argument 'userRoles'.
> {code}
> public RangerAccessRequestImpl(RangerAccessResource resource, String accessType, String user, Set<String> userGroups, Set<String> userRoles) {
> ...
> {code}
>  
> It would be great to make this constructor backward compatible because other Apache components, e.g., Apache Impala, is currently using the old constructor.
>  



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