ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-20628) Ambari doesn't set properties correctly
Date Thu, 13 Apr 2017 17:04:41 GMT


Hadoop QA commented on AMBARI-20628:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results:
Console output:

This message is automatically generated.

> Ambari doesn't set properties correctly
> ---------------------------------------
>                 Key: AMBARI-20628
>                 URL:
>             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, AMBARI-20628_v2.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

View raw message