[
https://issues.apache.org/jira/browse/AMBARI-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172772#comment-14172772
]
Hudson commented on AMBARI-7793:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #595 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/595/])
AMBARI-7793 On add service, the Cap scheduler is being expanded into individual
props. (ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=13b097c3d5b49d9ca709f42d2d3a29a3c401b8e1)
* ambari-web/test/controllers/wizard/step7_test.js
* ambari-web/app/controllers/wizard/step7_controller.js
> 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)
