You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2014/08/13 17:42:12 UTC
[jira] [Created] (AMBARI-6848) Service config version should always
clone and rev up (not simply point to an older version)
Dmytro Sen created AMBARI-6848:
----------------------------------
Summary: Service config version should always clone and rev up (not simply point to an older version)
Key: AMBARI-6848
URL: https://issues.apache.org/jira/browse/AMBARI-6848
Project: Ambari
Issue Type: Bug
Components: controller
Affects Versions: 1.7.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Blocker
Fix For: 1.7.0
When a user wants to "go back" (revert) to a set of configs for a specific serviceconfigversion, this should create a new serviceconfigversion.
For example: v1, v2, v3, v4 and v5 (current)
If user wants to "go back/revert" to v2 of the configs, they want to create v6 of the serviceconfigversion which is set to all the props of v2 (i.e. a clone).
--
This message was sent by Atlassian JIRA
(v6.2#6252)