You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Abhishek Kumar (Jira)" <ji...@apache.org> on 2025/02/10 22:48:00 UTC
[jira] [Updated] (RANGER-4990) Rationalize processing of match-types for policy and tag evaluation
[ https://issues.apache.org/jira/browse/RANGER-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Kumar updated RANGER-4990:
-----------------------------------
Fix Version/s: 2.6.0
> 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
> Fix For: 2.6.0
>
>
> 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)