[
https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491076#comment-14491076
]
Steve Loughran commented on YARN-2423:
--------------------------------------
Can I note that the compatibility guidelines already declare that the History
Server APIs (see
[http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html#REST_APIs]
, it's just that the link
"hadoop-yarn/hadoop-yarn-site/HistoryServerRest.html" doesn't resolve to
anything.
If YARN-2444 were to be altered so that the GET call was visible from
TimelineClient. then there wouldn't be an explicit API/model of the v1 APIs to
maintain, simply a REST view for callers to set up paths and do it themselves.
The advantage of doing it this way is to pick up the client's UGI/SPNEGO
integration, as well as its retry logic.
> TimelineClient should wrap all GET APIs to facilitate Java users
> ----------------------------------------------------------------
>
> Key: YARN-2423
> URL: https://issues.apache.org/jira/browse/YARN-2423
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Robert Kanter
> Attachments: YARN-2423.004.patch, YARN-2423.005.patch,
> YARN-2423.006.patch, YARN-2423.007.patch, YARN-2423.patch, YARN-2423.patch,
> YARN-2423.patch
>
>
> TimelineClient provides the Java method to put timeline entities. It's also
> good to wrap over all GET APIs (both entity and domain), and deserialize the
> json response into Java POJO objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
