[jira] [Commented] (AMBARI-23809) Identical sets of capacity scheduler properties are displayed as unequal ones in configs comparison view

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-23809:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9220/])
AMBARI-23809 Identical sets of capacity scheduler properties are (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=aefd00ac5c1e119afee6ccd39a5284600e794b98])
* (edit) ambari-web/app/mappers/configs/stack_config_properties_mapper.js


> Identical sets of capacity scheduler properties are displayed as unequal ones in configs comparison view
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-23809
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23809
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> While comparing different YARN config versions, capacity scheduler values are shown as different ones. The only displayed difference is the order of properties in those sets, though even the order is the same for both versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)