[
https://issues.apache.org/jira/browse/MAPREDUCE-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162583#comment-13162583
]
Hitesh Shah commented on MAPREDUCE-2863:
----------------------------------------
Comments
- some files show unused imports
- there are still quite some null checks on objects when initialized via
object constructors. In some cases, there are no try catch blocks hence these
null checks will never get triggered in any case as the ctor will likely throw
exceptions. In other cases, there is a null check after the try catch block
i.e. dead code.
Something to look into - not sure if this is caused by the framework. I came
across http://java.net/jira/browse/JERSEY-38 but not sure whether it is related
to the issue below yet.
- http://hrt11n07.cc1.ygridcore.net:8088/ws/v1/cluster/nodes/ returns a 404.
- http://hrt11n07.cc1.ygridcore.net:8088/ws/v1/cluster/nodes returns data.
( likely an issue with all resources )
General question on absent applications - querying for an absent app i.e. say
http://RM:8088/proxy/application_1323054018624_0004/ws/v1/mapreduce/info -
returns a 500 with a stack trace instead of a 404. From an api spec point of
view, this is not really an error but just a not found.
> Support web-services for RM & NM
> --------------------------------
>
> Key: MAPREDUCE-2863
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2863
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2, nodemanager, resourcemanager
> Affects Versions: 0.23.0
> Reporter: Arun C Murthy
> Assignee: Thomas Graves
> Priority: Blocker
> Attachments: MAPREDUCE-2863.patch, MAPREDUCE-2863.patch,
> MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, MAPREDUCE-2863.patch,
> MAPREDUCE-2863.patch, MAPREDUCE-2863.patch, amoutput.txt, appoutput.txt,
> hsoutput.txt, nmoutput.txt, nmoutput.txt, nmoutput.txt, rmoutput.txt,
> rmoutput.txt, rmoutput.txt
>
>
> It will be very useful for RM and NM to support web-services to export
> json/xml.
--
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
