Marcelo Vanzin commented on YARN-2423:

Hi Vinod,

I think the point that Robert was trying to make is that adding these APIs 
might force Yarn to maintain compatibility for it. So it would allow clients to 
code against the public API and have a reasonable expectation that it wouldn't 

But I understand that with the redesign it might be hard to maintain 
compatibility. I guess it's a choice you guys have to make, but the lack of a 
public, stable read API is definitely a barrier for Spark adopting this 
feature. (I understand we could write code to talk to the REST server directly, 
but you seem to imply that this approach would also run into compatibility 
issues after the redesign.)

> 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