You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Sandor Magyari (JIRA)" <ji...@apache.org> on 2017/03/30 13:54:41 UTC

[jira] [Updated] (AMBARI-20628) Ambari doesn't set properties correctly

     [ https://issues.apache.org/jira/browse/AMBARI-20628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandor Magyari updated AMBARI-20628:
------------------------------------
    Attachment: AMBARI-20628.patch

> Ambari doesn't set properties correctly
> ---------------------------------------
>
>                 Key: AMBARI-20628
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20628
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20628.patch
>
>
> When deploying a cluster with Blueprints using ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES as ConfigRecommendationStrategy, Ambari doesn't override properties with custom values specified in Blueprint. Ambari considers custom value if is not equal to stack default value. This means that you can't keep stack default value for a property if is stack advisor sets some value different then the stack default.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)