Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Fri, 15 Nov 2013 18:05:21 +0000 (UTC)
From: "Aleksandr Kovalenko (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12679444.1384537108090.81850.1384538721638@arcas>
In-Reply-To: <JIRA.12679444.1384537108090@arcas>
References: <JIRA.12679444.1384537108090@arcas>
Subject: [jira] [Commented] (AMBARI-3776) Non-default config-group configs
 should have +Exception action
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksandr Kovalenko commented on AMBARI-3776:
---------------------------------------------

committed to trunk

> Non-default config-group configs should have +Exception action
> --------------------------------------------------------------
>
>                 Key: AMBARI-3776
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3776
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3776.patch
>
>
> When I select a non-default config-group, I see most of the configs as disabled (because they were not overridden). However these do not have the +Exception action beside them. They should have the action, which when clicked simply adds an override row to enter the new value. Then the +Exception action should not be visible, but a -Remove action should be visible on the newly added override.


--
This message was sent by Atlassian JIRA
(v6.1#6144)