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-3401) [Data Model] users should not be able to create a generic TimelineEntity and associate arbitrary type
Date Sun, 29 Mar 2015 22:36:53 GMT

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

Zhijie Shen commented on YARN-3401:
-----------------------------------

IMHO, I think we can use ACL to control users' access to certain resources, but I agree with
Junping that we can come back to this issue after we have timeline service v2 functionality
work done.

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

Mime
View raw message