[ https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325243#comment-14325243 ]
Li Lu commented on YARN-3166: ----------------------------- Comments are more than welcome. Specifically, we may want to decide the arrangement on timeline aggregator first, since we may need to refactor part of the code. > [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)