[
https://issues.apache.org/jira/browse/MAPREDUCE-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126744#comment-13126744
]
Luke Lu commented on MAPREDUCE-2863:
------------------------------------
bq. So in conclusion the code sizes seems pretty comparable.
You call jersey's having to modify two files adding 100%+ more lines of code
besides 3 more annotations (you probably need 4 for the @Context as the jersey
snippet you post won't even compile) and an *unsafe* *cast* vs yarn webapp
(BTW, it's not Hamlet, which is a strictly a view technology)'s *type* *safe*
and concise solution comparable? Since rm and rmcontext is also used in two
other methods, you can essentially reduce the particular solution to one line.
Wait until you try to write a unit test for the method! The longer time you
spent figuring out yarn webapp details is probably because it's a new (and IMO
better) way of doing things via Guice, which has extensive documentation. I'll
add better docs for yarn webapp framework itself (which is pretty small) RSN :)
IMO, yarn webapp is far superior, which is already equivalent or better than
the draft JAX-RS 2.0 (still a *special* purpose DI solution), which obsoletes
JAX-RS 1.1 that jersey implements, because yarn webapp is backed by a superior
*general* purpose DI library: Guice, which is a reference implementation of a
(IMO) more useful Java standard (JSR-330).
> 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
> Reporter: Arun C Murthy
> Assignee: Thomas Graves
>
> 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
