[
https://issues.apache.org/jira/browse/RANGER-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-3937:
-----------------------------------
Description:
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.
was:Currently, the ranger plugins versions present as part of the respective
ranger-<service> images are based on the ranger admin version whereas they can
have their own independent versions. This will allow ranger plugins to interact
with ranger with both of them being on different versions.
> 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: Bug
> Components: Ranger
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0
>
>
> 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)
