[
https://issues.apache.org/jira/browse/YARN-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382412#comment-14382412
]
Naganarasimha G R commented on YARN-3401:
-----------------------------------------
Hi [~sjlee0], IIRC as part of the doc or some jira discussion we discussed
that only RM/NM should be able to send the YARN system entities and other
clients should not be able to send, right ? do we need to completely block it ?
if so if we add a check @ Timelineclient will it impact NM from posting
container metrics & entities ?
> [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)
