hadoop-yarn-issues mailing list archives

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

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

Zhijie Shen commented on YARN-3041:
-----------------------------------

bq. Is it up to the calling code to make sure that if it sets entity A as the parent of entity
B, that it also sets entity B as the child of entity A and vice versa?

In the pervious patch. If we correlate two entities, it's easy to implement the logic in the
data object itself to enforce the relation integrity. However, for the aforementioned reason,
the relates/is related entities and parent/children entities become IDs, we can not simply
do the check. Caller needs to make sure the relationship be properly set. At the server side,
we need to do the check too. Thoughts?

> [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.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
(v6.3.4#6332)

Mime
View raw message