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

Sangjin Lee commented on YARN-3166:
-----------------------------------

{quote}
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.
{quote}

Just to note the obvious, that would not work if it is a public interface that 
other code implements. If it is internal, yes, we could evolve the interface 
that way, but it is a public interface, that is not an option... So for 
TimelineClient specifically, I think it is true. But as a general rule, I think 
there could be issues...

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