Zhijie Shen commented on YARN-2423:

It seems that Spark wants the stable APIs. But we know, based on the new data 
model, APIs will be changed accordingly. One step back, even the APIs are not 
changed, we usually be a bit conservative to mark them \@Unstable in the 
release where they're pushed out.

bq. Coming to the patch itself, I feel getEntity is a special case of 
getEntities. To limit the number of new APIs being added, can we get rid of it?

They're wrapping different REST APIs. One get and one search, though we can 
narrow down the result set to one entity. If we want to move on with it, I 
suggest keeping both.

> 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