Pradeep Agrawal created RANGER-2019:
---------------------------------------
Summary: Handle upgrade scenario to rename the old ATLAS service
def and use the new service def
Key: RANGER-2019
URL: https://issues.apache.org/jira/browse/RANGER-2019
Project: Ranger
Issue Type: Improvement
Components: Ranger
Affects Versions: 1.1.0
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal
Fix For: 1.1.0
Based on [this RANGER-2004
commit|https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=9a3d4e306b5e536e294cb20fb67664e2e0b7a7f8],
Atlas service def is updated. During the upgrade of existing env, old Atlas
service def should be renamed so that new service def can be used.
During migration to Ranger 1.1.0, this Jira should address the following:
# Check for service-def named 'atlas'. If it is not found - nothing more to do.
# Rename all service instances of type 'atlas', with the addition of a suffix
"-v1". Existing service named 'cl1_atlas' will become 'cl1_atlas-v1'. If
'cl1_atlas-v1' already exists, append an count like 'cl1_atlas-v1.1',
'cl1_atlas-v1-2'
# After all service instances are renamed, rename service-def as 'atlas-v1'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
