hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joep Rottinghuis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3041) [Data Model] create overall data objects of TS next gen
Date Wed, 18 Feb 2015 17:06:13 GMT

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

Joep Rottinghuis commented on YARN-3041:

Some additional throughs:
If we have the types strongly typed, do we need to call containers "YARN_CONTAINER" and "YARN_FLOW",
or would we be able to capture more generic flows and containers with this as well ?
Perhaps the framework used to run could be a property for the generic entity.

I don't see what the advantage is to have the user set up the proper relationship. Why not
make that part of the constructors and have protected methods to set up the hierarchy correctly
? Why introduce a chance to have this all set up strange ?

I think the acceptable entity types for parent-child relationships can be setup in the enum
itself. The enums would simply have methods on them and can take constructors.

> [Data Model] create overall data objects of TS next gen
> -------------------------------------------------------
>                 Key: YARN-3041
>                 URL: https://issues.apache.org/jira/browse/YARN-3041
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Zhijie Shen
>         Attachments: Data_model_proposal_v2.pdf, YARN-3041.2.patch, YARN-3041.3.patch,
YARN-3041.4.patch, YARN-3041.preliminary.001.patch
> Per design in YARN-2928, create the ATS entity and events API.
> Also, as part of this JIRA, create YARN system entities (e.g. cluster, user, flow, flow
run, YARN app, ...).

This message was sent by Atlassian JIRA

View raw message