hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components
Date Wed, 18 Feb 2015 00:56:12 GMT

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

Li Lu commented on YARN-3166:
-----------------------------

Some notes about the current code organization arrangements:

# *API records*: classes should be consistent with YARN-3041. 
# *Client*: Currently we would like to extend the existing timeline service client. We’re
planning to extend the API of the current client by adding more support to our v2 object model.
We may also mark existing methods in timeline client as deprecated. In phase 1, we are not
planning to add async client support. 
# *Storage*: TimelineStorage should contain all APIs for the DAO layer. A TimelineStorageImpl
implements required methods used by TimelineStorage. (Same as the current storage layer. )


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

Mime
View raw message