ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20628) Ambari doesn't set properties correctly
Date Fri, 31 Mar 2017 13:02:41 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-20628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950822#comment-15950822
] 

Sandor Magyari commented on AMBARI-20628:
-----------------------------------------

Committed to trunk:

{code}
commit 9741236f3c8b4a8a293fa0b7db5c64c0e7aa704d
Author: Sandor Magyari <smagyari@hortonworks.com>
Date:   Thu Mar 30 12:04:19 2017 +0200

    AMBARI-20628. Ambari doesn't set properties correctly (magyari_sandor)
{code}

> 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)

Mime
View raw message