You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/05/27 02:29:18 UTC
[jira] [Commented] (AMBARI-11399) Merged Stack Configurations Don't
Use Overrides On Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-11399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560202#comment-14560202 ]
Hudson commented on AMBARI-11399:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2717 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2717/])
AMBARI-11399 - Merged Stack Configurations Don't Use Overrides On Upgrade (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d14f044445a2f768ed0e8375279821c3a7daab5c)
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
* ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
> Merged Stack Configurations Don't Use Overrides On Upgrade
> ----------------------------------------------------------
>
> Key: AMBARI-11399
> URL: https://issues.apache.org/jira/browse/AMBARI-11399
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.0
>
>
> When upgrading between HDP 2.2 and HDP 2.3, the merged configurations are not taking an override that exists in HDP 2.3 if the property was originally defined in HDP 2.2. For example:
> HDP 2.2: foo=bar
> HDP 2.3: foo=baz
> If the current value on the installed cluster is "bar" then then it was not customized and the new value of "baz" should be used. Only if the current stack value doesn't equal "bar" should the original value be preserved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)