Hadoop QA commented on AMBARI-18609:

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

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

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

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

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

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

Test results: 
Console output: 

This message is automatically generated.

> Implement a way to configure Stack Upgrade Merger to skip particular 
> properties to be merged from stack defaults
> ----------------------------------------------------------------------------------------------------------------
>                 Key: AMBARI-18609
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18609
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Dmytro Grinenko
>            Priority: Critical
>             Fix For: trunk
>         Attachments: AMBARI-18609.patch
> We need to reincarnate on-stack-upgrade feature in less functionality way. 
> It's true, that we don't need an analog to Stack Advisor or Upgrade Packs, 
> however we need a way to exclude some property from being merged with stack 
> defaults during Upgrade.
> Why we need this: there could be a lot of situations, when we need some 
> properties only in some 
> picante moments, and these properties regulated according to Stack 
> Advisor/Wizards or another internal state. In this case, these properties 
> shipped with dummy stack default values, which are incorrect.

This message was sent by Atlassian JIRA

Reply via email to