[
https://issues.apache.org/jira/browse/MAPREDUCE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-3792:
-------------------------------------
Target Version/s: 0.23.2 (was: 0.23.3, 0.23.2, 0.24.0)
Status: Open (was: Patch Available)
On second thoughts, the code to deal with 'no access' being spread over the RM
and the client (admittedly, only for display) bothers me a little.
How about return a static DUMMY_APPLICATION_RESOURCE_USAGE_REPORT with all
fields zeroed out (say set to -1) in case of 'no access' from RM to the client?
We should also document this behaviour via javadoc.
Some minor nits:
# Use a constant rather than the string 'N/A'
# Maybe the parameter should be called allowAccess rather than
fullAccessAllowed, or maybe I'm being too sensitive! :)
> job -list displays only the jobs submitted by a particular user
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-3792
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3792
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Ramya Sunil
> Assignee: Jason Lowe
> Priority: Critical
> Attachments: MAPREDUCE-3792.patch, MAPREDUCE-3792.patch
>
>
> "mapred job -list" lists only the jobs submitted by the user who ran the
> command. This behavior is different from 1.x.
--
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
