Li Lu commented on YARN-3166:

I've updated the proposed package/module structures. We may want to refactor 
some of our existing aggregator code, mainly changing their names. Here are the 
latest version:

h4. Module: hadoop-yarn-api
* package: {{o.a.h.yarn.api.records.timelineservice}}
** ApplicationEntity, ApplicationAttemptEntity, ClusterEntity, ContainerEntity, 
FlowEntity, FlowRunEntity, HierarchicalTimelineEntity, TimelineEntity
** TimelineEvent
** TimelineMetric
** TimelineQueue
** TimelineUser

h4. Module: hadoop-yarn-client
* package: {{o.a.h.yarn.client.api}}
** TimelineClient

* package: {{o.a.h.yarn.client.api.impl}} 
** TimelineClientImpl

h4. Module: hadoop-yarn-server/hadoop-yarn-server-timelineservice
* package: {{o.a.h.yarn.server.timelineservice.aggregator}}
** BaseAggregatorService -> BaseTimelineAggregator
** AppLevelAggregatorService -> AppLevelTimelineAggregator
** AppLevelServiceManager -> TimelineAggregatorsCollection
** AppLevelServiceProvider -> (TODO: Remove or rename)
** PerNodeAggregatorServer -> PerNodeTimelineAggregatorsAuxService
** PerNodeAggregatorWebService -> TimelineAggregatorWebService

* package: {{o.a.h.yarn.server.timelineservice.reader}}
** TimelineReader
** TimelineReaderPool

* package: {{o.a.h.yarn.server.timelineservice.storage}}
** TimelineStorage
** TimelineStorageImpl
** HBaseTimelineStorageImpl
** PhoenixTimelineStorageImpl
** InMemTimelineStorageImpl

h4. Under hadoop-yarn-common
For common YARN libraries. Modules/libraries added into this directory need to 
be decided on a case-by-case basis. 

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

Reply via email to