Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 3 Apr 2012 19:04:25 +0000 (UTC)
From: "Anupam Seth (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <676433630.7816.1333479865269.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <561426423.22963.1331872098093.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-4020) Web services returns incorrect
 JSON for deep queue tree
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anupam Seth updated MAPREDUCE-4020:
-----------------------------------

    Attachment: MAPREDUCE-4020-branch-23.patch

Thanks for the review Tom! Re-sttaching patch with the missing license header.
                
> Web services returns incorrect JSON for deep queue tree
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-4020
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4020
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, webapps
>    Affects Versions: 0.23.1
>            Reporter: Jason Lowe
>            Assignee: Anupam Seth
>         Attachments: MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, MAPREDUCE-4020-branch-23.patch, testcase.patch
>
>
> When the capacity scheduler is configured for more than two levels of queues, the web services API returns incorrect JSON for the subQueues field of some parent queues.  The "subQueues" field for parent queues should always be an array, but sometimes the field appears multiple times for a queue and as what looks like a CapacityQueueInfo object instead of an array.  Besides the sometimes-an-array-sometimes-not problem, parsing the result into a JSON object causes all but the last "subQueues" field to be discarded since they are overwritten by subsequent fields with the same name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira