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

Hitesh Shah commented on YARN-2423:
-----------------------------------

bq. This is based on the current implementation. We can try to add a 
compatibility layer or something in another JIRA. Though I'm not sure how 
feasible that will be; the data models are somewhat different.

If the current implementation is not planned to be supported in the long term, 
why introduce a java API that will soon be deprecated or rendered obsolete if 
the data models are different? Or is the only intention to backport this 
feature/API into 2.4, 2.5 and 2.6 for existing users of the current 
implementation of ATS?

 



> 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