You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2017/04/25 09:47:04 UTC

[jira] [Resolved] (RANGER-1478) Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many times

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

Colm O hEigeartaigh resolved RANGER-1478.
-----------------------------------------
    Resolution: Fixed

> Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many times
> -----------------------------------------------------------------------------------
>
>                 Key: RANGER-1478
>                 URL: https://issues.apache.org/jira/browse/RANGER-1478
>             Project: Ranger
>          Issue Type: Improvement
>          Components: plugins
>    Affects Versions: 0.7.0
>            Reporter: Zsombor Gegesy
>            Assignee: Zsombor Gegesy
>            Priority: Minor
>              Labels: code-cleanup
>             Fix For: 1.0.0
>
>         Attachments: 0001-RANGER-1478-Small-refactor-in-RangerPolicyEngineCach.patch
>
>
> RangerPolicyEngineOptions has a lot of public fields, which is written from various places from the code base, which should be avoided. That object is configured from RangerConfiguration, but in the middle of the plugin initialization code, which makes this a bit more complex, than it should be.
> Suggestions:
> * RangerConfiguration should be treated as an object, not a static facade for a couple of config values
> * RangerPolicyEngineOptions should get his configuration from directly the RangerConfiguration, in an explicit, encapsulated way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)