[ https://issues.apache.org/jira/browse/AMBARI-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512493#comment-14512493 ]
Hudson commented on AMBARI-10739: --------------------------------- SUCCESS: Integrated in Ambari-trunk-Commit #2439 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2439/]) AMBARI-10739. ConfigureAction Must Take Into Account Stack Versions (ncole) (ncole: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=682d82eef2e1229f4aaf9cd217c27c4c857d37fe) * ambari-server/src/main/java/org/apache/ambari/server/state/Config.java * ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/ConfigureAction.java * ambari-server/src/main/java/org/apache/ambari/server/state/ConfigImpl.java * ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/ConfigureActionTest.java * ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureTask.java > ConfigureAction Must Take Into Account Stack Versions > ----------------------------------------------------- > > Key: AMBARI-10739 > URL: https://issues.apache.org/jira/browse/AMBARI-10739 > Project: Ambari > Issue Type: Task > Components: ambari-server > Reporter: Nate Cole > Assignee: Nate Cole > Fix For: 2.1.0 > > Attachments: AMBARI-10739.patch > > > The {{ConfigureAction}} that is used in the rolling upgrade process blindly > creates new configurations for every single change that is listed in the > upgrade pack. This needs to change in two fundamental ways: > - When upgrading or downgrading within a stack version (hdp-2.2.x.x to > hdp-2.2.y.y), before making a new configuration with the value from the > upgrade pack, compare the value to the current value. If they are the same, > do no work > - When upgrading across stack versions (hdp-2.2 to hdp-2.3), new > configurations are already being created. There is no need to create new > configurations since the upgrade has already done this. The desired > configurations should simply be modified with the new values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)