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 2019/11/27 13:32:00 UTC
[jira] [Updated] (RANGER-2652) Refactor policy engine
[ https://issues.apache.org/jira/browse/RANGER-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Velmurugan Periasamy updated RANGER-2652:
-----------------------------------------
Fix Version/s: (was: master)
> Refactor policy engine
> ----------------------
>
> Key: RANGER-2652
> URL: https://issues.apache.org/jira/browse/RANGER-2652
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: 2.1.0
>
>
> Objectives are:
> # Encapsulate Ranger policy evaluators into a class (PolicyEngine)
> # Separate Ranger Policy Engine APIs based on their users (plugin or ranger-admin), and define corresponding wrapper interfaces (RangerPolicyEngine and RangerServicePoliciesAdmin). Provide their respective implementation classes.
> # Remove unused functionality (keeping usage-counts, re-ordering policy-evaluators based on their usage, etc.)
> # Separate out request preprocessing into a separate interface (RangerAccessRequestProcessor) which wraps context-enrichers and roles for pre-processing/enriching access request.
> # Optimize Trie for incremental changes (adds/deletes)
> # Assorted code clean-up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)