You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2015/12/02 20:38:11 UTC

[jira] [Updated] (RANGER-763) Optimize policy evaluation by reordering match-checks

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

Madhan Neethiraj updated RANGER-763:
------------------------------------
    Attachment: 0001-RANGER-763-Optimize-policy-evaluation-by-reordering-.patch

> Optimize policy evaluation by reordering match-checks
> -----------------------------------------------------
>
>                 Key: RANGER-763
>                 URL: https://issues.apache.org/jira/browse/RANGER-763
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>    Affects Versions: 0.5.0
>            Reporter: Madhan Neethiraj
>            Assignee: Abhay Kulkarni
>            Priority: Minor
>             Fix For: 0.6.0
>
>         Attachments: 0001-RANGER-763-Optimize-policy-evaluation-by-reordering-.patch
>
>
> To improve the policy-engine performance, the evaluation should attempt resource-match only after verifying that the policy can possibly make the decision for the user/groups/access-type in the request. This optimization should be done only after "isAudited" flag is determined - as audit depends only on resource-match (and not the user/groups/access-type match).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)