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

Hadoop QA commented on AMBARI-22431:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12897376/AMBARI-22431-v2.patch
  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:red}-1 javac{color}.  The patch appears to cause the [build to 
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12662//artifact/patch-work/patchJavacWarnings.txt].

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12662//console

This message is automatically generated.

> Able to add config type if EU/RU of the same stack (minor version upgrade)
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-22431
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22431
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: 2.6.1
>
>         Attachments: AMBARI-22431-v2.patch, AMBARI-22431.patch
>
>
> EU/RU does not create/load default of new config types when the source stack 
> and target stack is the same. This JIRA introduces a new config task type for 
> creating/loading defaults of a new config type when stack does not change 
> during EU/RU. This is particularly important for EU/RU of custom services  
> where their stack may not change at all.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to