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

Hadoop QA commented on AMBARI-10653:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12727205/AMBARI-10653.patch
  against trunk revision .

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2456//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2456//console

This message is automatically generated.

> Configs in theme should show up even when not defined in stack
> --------------------------------------------------------------
>
>                 Key: AMBARI-10653
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10653
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10653.patch
>
>
> Imagine that we have just upgraded from Ambari-2.0.0 to Ambari-2.1.0. None of 
> the new configs we have added (like Hive's hive_txn_acid) will be available 
> in the configs. Because of that, when I go to Hive's config page, there will 
> be no config with toggle.
> We want to show in UI, configs that are there in the theme, but not set in 
> the cluster. When saved, the config values should be persisted on server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to