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

Zhijie Shen commented on YARN-3166:
-----------------------------------

bq. In such a scenario if we try to Reuse REST then we might end up with lot of 
If else...

I'm not sure if I understand your question correction, but I think we may not 
end up with lot of if/else. The proposal is:

1. In TimelineClient, we keep the existing methods that operate on the old data 
model, but mark them deprecated individually.

2. In TimelineClient, we create the new methods that operate on the new data 
model.

The methods of operating new and old data models are separated.

> [Source organization] Decide detailed package structures for timeline service 
> v2 components
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-3166
>                 URL: https://issues.apache.org/jira/browse/YARN-3166
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Li Lu
>            Assignee: Li Lu
>
> Open this JIRA to track all discussions on detailed package structures for 
> timeline services v2. This JIRA is for discussion only.
> For our current timeline service v2 design, aggregator (previously called 
> "writer") implementation is in hadoop-yarn-server's:
> {{org.apache.hadoop.yarn.server.timelineservice.aggregator}}
> In YARN-2928's design, the next gen ATS reader is also a server. Maybe we 
> want to put reader related implementations into hadoop-yarn-server's:
> {{org.apache.hadoop.yarn.server.timelineservice.reader}}
> Both readers and aggregators will expose features that may be used by YARN 
> and other 3rd party components, such as aggregator/reader APIs. For those 
> features, maybe we would like to expose their interfaces to 
> hadoop-yarn-common's {{org.apache.hadoop.yarn.timelineservice}}? 
> Let's use this JIRA as a centralized place to track all related discussions. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to