ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.T. Moore (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-14712) Advanced service properties are not sorted consistently within sections
Date Mon, 18 Jan 2016 20:34:39 GMT
J.T. Moore created AMBARI-14712:
-----------------------------------

             Summary: Advanced service properties are not sorted consistently within sections
                 Key: AMBARI-14712
                 URL: https://issues.apache.org/jira/browse/AMBARI-14712
             Project: Ambari
          Issue Type: Improvement
          Components: ambari-web
    Affects Versions: 2.2.0
            Reporter: J.T. Moore
            Priority: Critical


When viewing the advanced properties for a service on two different Ambari managed clusters,
the properties do not appear in a same order within each section. Using the Advanced hdfs-site
section as an example, the "dfs.block.access.token.enable" property may appear at the top
of the section on one cluster, but may it may appear somewhere in the middle of the section
on another cluster. This makes comparing advanced property settings across clusters very cumbersome
and time consuming. A simiple solution would be to sort the properties alphabetically by display_name
within each section.



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

Mime
View raw message