You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2015/03/26 19:33:00 UTC

[jira] [Commented] (YARN-3401) [Data Model] users should not be able to create a generic TimelineEntity and associate arbitrary type

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

Junping Du commented on YARN-3401:
----------------------------------

We also need to make sure compatibility between old version application and new version timeline service. Typically, it won't be the case. But just put here as a reminder.

> [Data Model] users should not be able to create a generic TimelineEntity and associate arbitrary type
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3401
>                 URL: https://issues.apache.org/jira/browse/YARN-3401
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Naganarasimha G R
>
> IIUC it is possible for users to create a generic TimelineEntity and set an arbitrary entity type. For example, for a YARN app, the right entity API is ApplicationEntity. However, today nothing stops users from instantiating a base TimelineEntity class and set the application type on it. This presents a problem in handling these YARN system entities in the storage layer for example.
> We need to ensure that the API allows only the right type of the class to be created for a given entity type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)