[
https://issues.apache.org/jira/browse/RANGER-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896833#comment-17896833
]
Abhay Kulkarni edited comment on RANGER-4990 at 11/14/24 9:27 PM:
------------------------------------------------------------------
Commit details:
master:
[https://github.com/apache/ranger/commit/2a340fa6614bafb90e071ee05d60b53ab87d8ed7]
ranger-2.6:
https://github.com/apache/ranger/commit/30883cf941dde13882ab4d8d5f94d4cd5e52e0da
was (Author: abhayk):
Commit details:
master:
https://github.com/apache/ranger/commit/2a340fa6614bafb90e071ee05d60b53ab87d8ed7
> Rationalize processing of match-types for policy and tag evaluation
> -------------------------------------------------------------------
>
> Key: RANGER-4990
> URL: https://issues.apache.org/jira/browse/RANGER-4990
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
>
> Policies/tags are selected for processing based on how the they match the
> accessed resource. The logic for the selection of policies/tags depends on
> # resourceMatchingScope specified in the access request, and
> # if the type of access desired is of type 'any'.
> The logic for the selection is inconsistent and hard to reason about.
> Additionally, code referencing the resourceMatchingScope does not check for
> null-ness. This may cause NullPointerExceptions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
