Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 15 Oct 2014 18:10:34 +0000 (UTC)
From: "Andrii Babiichuk (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12748338.1413393170000.272418.1413396634087@Atlassian.JIRA>
In-Reply-To: <JIRA.12748338.1413393170000@Atlassian.JIRA>
References: <JIRA.12748338.1413393170000@Atlassian.JIRA>
 <JIRA.12748338.1413393170938@arcas>
Subject: [jira] [Commented] (AMBARI-7793) On add service, the Cap scheduler
 is being expanded into individual props
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrii Babiichuk commented on AMBARI-7793:
------------------------------------------

committed to trunk and branch 1.7.0

> On add service, the Cap scheduler is being expanded into individual props
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-7793
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7793
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Blocker
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7793.patch, AMBARI-7793_branch-1.7.0.patch
>
>
> 1. Go to add service
> 2. An Customize Configs, all the capacity scheduler configs are expanded in name=value properties, in addition to showing the "Scheduler" content area. They should not have been expanded.


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