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/10/24 16:10:00 UTC

[jira] [Updated] (RANGER-2625) Plugin capability/compatibility model

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

Velmurugan Periasamy updated RANGER-2625:
-----------------------------------------
    Fix Version/s: 2.1.0

> Plugin capability/compatibility model
> -------------------------------------
>
>                 Key: RANGER-2625
>                 URL: https://issues.apache.org/jira/browse/RANGER-2625
>             Project: Ranger
>          Issue Type: New Feature
>          Components: Ranger
>    Affects Versions: master
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: 2.1.0
>
>
> When features and capabilities are added to Ranger, it is possible to get into situation where users/admins may write policies using new capabilities that are not available in the deployed plugins. As a first step towards understanding and ensuring version compatibility between ranger-admin and plugins, it is desirable that plugin reports features/capabilities that it supports to ranger-admin periodically, and ranger-admin persists this information for review.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)