Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CCCE10DAB for ; Wed, 18 Feb 2015 00:56:13 +0000 (UTC) Received: (qmail 24874 invoked by uid 500); 18 Feb 2015 00:56:13 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 24831 invoked by uid 500); 18 Feb 2015 00:56:12 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 24818 invoked by uid 99); 18 Feb 2015 00:56:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2015 00:56:12 +0000 Date: Wed, 18 Feb 2015 00:56:12 +0000 (UTC) From: "Li Lu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3166?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14325= 231#comment-14325231 ]=20 Li Lu commented on YARN-3166: ----------------------------- Some notes about the current code organization arrangements: # *API records*: classes should be consistent with YARN-3041.=20 # *Client*: Currently we would like to extend the existing timeline service= client. We=E2=80=99re planning to extend the API of the current client by = adding more support to our v2 object model. We may also mark existing metho= ds in timeline client as deprecated. In phase 1, we are not planning to add= async client support.=20 # *Storage*: TimelineStorage should contain all APIs for the DAO layer. A T= imelineStorageImpl implements required methods used by TimelineStorage. (Sa= me as the current storage layer. ) > [Source organization] Decide detailed package structures for timeline ser= vice 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 fo= r 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 YAR= N and other 3rd party components, such as aggregator/reader APIs. For those= features, maybe we would like to expose their interfaces to hadoop-yarn-co= mmon's {{org.apache.hadoop.yarn.timelineservice}}?=20 > Let's use this JIRA as a centralized place to track all related discussio= ns.=20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)