[jira] [Commented] (AMBARI-1409) Normalize all category/property/metric names available through the API

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

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

Tom Beerbower commented on AMBARI-1409:
---------------------------------------

Right now the metric names already have a public name to internal name mapping in ganglia_properties.json and jmx_properties.json.  We may be able to add an alias field to the mapping that would allow us to keep the old public names for some period of time while we switch over to the normalized public names.
                
> Normalize all category/property/metric names available through the API
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-1409
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1409
>             Project: Ambari
>          Issue Type: Sub-task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 1.3.0
>
>
> There is no standard for the property names available through the API. For the most part, the public name of a metric is the same as the internal name from the back end (Ganglia, JMX, Ambari DB). This includes a mix of upper case, lower case, camel case, underscore, dashes, etc... We should define a standard for the public facing names that we expose through the API. We need to come up with a mechanism that exposes the new public names but also makes the existing names available for some time (unless we simply cut over to the new names for the next API version).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira