[ 
https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345976#comment-14345976
 ] 

Marcelo Vanzin commented on YARN-2423:
--------------------------------------

We'd rather not depend on unstable APIs. But in this context, what does 
"Unstable" mean? When ATS v2 is released, will all support for ATS v1 be 
removed? Are you gonna change all the APIs to work against v2, making code 
built against v1 effectively broken?

I'd imagine that if v2 is really incompatible you'd add a new set of APIs and 
then deprecate v1 instead. The v1 APIs would be public, stable and deprecated 
at that point.

> 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)

Reply via email to