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 2018/03/07 23:19:00 UTC

[jira] [Updated] (RANGER-1578) Ranger plugins should use default service-def when it fails to obtain from Ranger Admin or cache

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

Velmurugan Periasamy updated RANGER-1578:
-----------------------------------------
    Fix Version/s: 1.0.0

> Ranger plugins should use default service-def when it fails to obtain from Ranger Admin or cache
> ------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1578
>                 URL: https://issues.apache.org/jira/browse/RANGER-1578
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>    Affects Versions: 0.7.0, master
>            Reporter: Madhan Neethiraj
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: 1.0.0, master, 0.7.1
>
>
> Ranger plugins obtain service-def at runtime from Ranger Admin. This enables  the plugins to receive the latest service-def, which might have been updated to use custom conditions, context-enrichers, etc. However, if the plugin fails to obtain the service-def from Ranger Admin (or from local-cache), it should use a default version of service-def - against which the plugin was developed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)