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 2024/07/27 00:00:17 UTC

[jira] [Updated] (RANGER-3937) Docker: Add capability to run ranger plugins and services with their own versions

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

Madhan Neethiraj updated RANGER-3937:
-------------------------------------
    Issue Type: Improvement  (was: Bug)

> Docker: Add capability to run ranger plugins and services with their own versions
> ---------------------------------------------------------------------------------
>
>                 Key: RANGER-3937
>                 URL: https://issues.apache.org/jira/browse/RANGER-3937
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>    Affects Versions: 2.4.0
>            Reporter: Abhishek Kumar
>            Assignee: Abhishek Kumar
>            Priority: Major
>             Fix For: 3.0.0, 2.5.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, the versions of ranger plugins and services(including ranger usersync and ranger tagsync) present as part of the respective ranger-<service> images are based on the ranger admin version whereas they can have their own versions independent of ranger admin version. This will allow ranger plugins to interact with ranger while being on different versions.
> for ex: ranger-hadoop and ranger-hive images run with plugin version 2.2.0 whereas ranger-admin image runs with version 2.3.0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)