Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 16 May 2013 20:31:16 +0000 (UTC)
From: "Kendall Thrapp (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12648043.1368736169025.334838.1368736276432@arcas>
In-Reply-To: <JIRA.12648043.1368736169025@arcas>
References: <JIRA.12648043.1368736169025@arcas>
Subject: [jira] [Created] (YARN-691) Invalid NaN values in Hadoop REST API
 JSON response
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kendall Thrapp created YARN-691:
-----------------------------------

             Summary: Invalid NaN values in Hadoop REST API JSON response
                 Key: YARN-691
                 URL: https://issues.apache.org/jira/browse/YARN-691
             Project: Hadoop YARN
          Issue Type: Bug
          Components: resourcemanager
    Affects Versions: 0.23.6
            Reporter: Kendall Thrapp


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 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