You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Benoy Antony (JIRA)" <ji...@apache.org> on 2014/11/15 17:03:34 UTC
[jira] [Updated] (HADOOP-11308) Enable JMX to directly output JSON
objects instead JSON strings
[ https://issues.apache.org/jira/browse/HADOOP-11308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoy Antony updated HADOOP-11308:
----------------------------------
Status: Patch Available (was: Open)
> Enable JMX to directly output JSON objects instead JSON strings
> ---------------------------------------------------------------
>
> Key: HADOOP-11308
> URL: https://issues.apache.org/jira/browse/HADOOP-11308
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.5.1
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HADOOP-11308.patch
>
>
> Currently many JMX beans provide Json content as strings.
> JMXJsonServlet outputs these as Json Strings. This also results in losing the original Json object structure.
> An example is given below:
> {code}
> "TieredStorageStats" : "{\"ARCHIVE\":{\"capacityTotal\":1498254102528,\"capacityUsed\":12288,\"capacityRemaining\":980102602752,\"blockPoolUsed\":12288,\"nodesInService\":3,\"numBlocks\":0}...
> {code}
> {code}
> "TieredStorageStats" : {"ARCHIVE":{"capacityTotal":1498254102528,"capacityUsed":12288,"capacityRemaining":980102602752,"blockPoolUsed":12288,"nodesInService":3,"numBlocks":0}...
> {code}
> In the former output {{TieredStorageStats}} maps to a JSON string while in the latter one it maps to a JSON object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)