Vinod Kumar Vavilapalli commented on YARN-2423:

[~rkanter], I am just pointing that the existing users today directly use the 
raw TimelineClient APIs. Adding a new API for an older framework we are 
rewriting anyways is backwards to me and additional burden of compatibility - 
unless we can write these new APIs in such a way that we know for sure that we 
will support them in the YARN-2928 rewrite.

[~vanzin], can Spark use the existing Timeline APIs that we already support and 
trying to maintain compatibility for MapReduce, Tez and Hive projects? The 
problem is that even if we implement the proposal in this JIRA, come YARN-2928, 
these new APIs may break and so Spark will have to add shim layers in either 

> 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

Reply via email to