[
https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337670#comment-14337670
]
Vinod Kumar Vavilapalli commented on YARN-2423:
-----------------------------------------------
Sorry, I misspoke. Yes, without this patch, they are the REST APIs; that is all
we have.
bq. Are they declared as "InterfaceAudience(Public)"? If they're not, we're not
willing to use those in Spark, because there's no commitment from Yarn to keep
them stable.
In my opinion, the APIs being added in this JIRA are no more stable than the
REST APIs. They will possibly change the moment our data-model via YARN-2928
changes and correspondingly the REST APIs change. So, If Spark doesn't want to
code against this in a shimmed layer, I am not sure I can be of much help.
FWIW, I am trying as much to maintain compatibility of what exists so far.
I'm not trying to block this patch, just pointing out potential breakages in
the near future given YARN-2928.
> 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)
