[jira] [Moved] (HADOOP-10123) Invalid NaN values in Hadoop REST API JSON response

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

     [ https://issues.apache.org/jira/browse/HADOOP-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Eagles moved YARN-691 to HADOOP-10123:
-----------------------------------------------

          Component/s:     (was: resourcemanager)
        Fix Version/s:     (was: 2.3.0)
    Affects Version/s:     (was: 2.0.4-alpha)
                           (was: 0.23.6)
                       0.23.6
                       2.0.4-alpha
           Issue Type: Improvement  (was: Bug)
                  Key: HADOOP-10123  (was: YARN-691)
              Project: Hadoop Common  (was: Hadoop YARN)

> Invalid NaN values in Hadoop REST API JSON response
> ---------------------------------------------------
>
>                 Key: HADOOP-10123
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10123
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.0.4-alpha, 0.23.6
>            Reporter: Kendall Thrapp
>            Assignee: Chen He
>         Attachments: Yarn-691.patch
>
>
> I've been occasionally coming across instances where Hadoop's Cluster Applications REST API (http://hadoop.apache.org/docs/r0.23.6/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Applications_API) has returned JSON that PHP's json_decode function failed to parse.  I've tracked the syntax error down to the presence of the unquoted word NaN appearing as a value in the JSON.  For example:
> "progress":NaN,
> NaN is not part of the JSON spec, so its presence renders the whole JSON string invalid.  Hadoop needs to return something other than NaN in this case -- perhaps an empty string or the quoted string "NaN".



--
This message was sent by Atlassian JIRA
(v6.1#6144)