Robert Kanter commented on YARN-2423:

Even if ATS v2 makes it for 2.8, I imagine it won't be fully stable; I'm 
assuming we're not going to suddenly throw away the old ATS in 2.8, right?  We 
have to mark it deprecated and leave it in for a few releases, especially if 
the new ATS isn't 100% ready yet.  

We seem to be assuming that this API won't be compatible with the new ATS.  I 
agree; it likely won't.  That also means that the REST API won't either.  So, 
regardless of whether or not we add this Java API, users will have to rewrite 
their code to use a new API.  Given that, it's a lot easier and cleaner for 
Java users to rewrite their code from one Java API to another Java API, than it 
is to rewrite their custom wrapped REST API and JSON handling code (which they 
also have to write themselves) to a new Java API (and that's assuming we ship a 
new Java API in 2.8; what if we only have another REST API?  That would be even 
harder for users).
And if the API turns out to be compatible, then we're already ahead of the 
game.  Either way, it seems like it would be easier for everyone if we put in 
this API, even if it's going to be "obsolete".

Keep in mind that even if it only lasts one release, not everyone updates their 
cluster every time a new Hadoop release is out.  There are many users who will 
stay on 2.7 (or distributed derived therefrom) for quite a while and would 
benefit from this API in the mean time.

> 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