[
https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382361#comment-14382361
]
Sangjin Lee commented on YARN-3044:
-----------------------------------
That's a fair point. As a rule, we need to prevent users of the TimelineEntity
API from setting arbitrary types. The only way of creating a YARN app timeline
entity for example should be through instantiating ApplicationEntity.
We may need to make some of the methods that make this possible non-public,
etc., although it remains to be seen how much of that is doable, given json
needs to be able to handle them.
If we have that, IMO the type-based casting should be acceptable (it should
reject the entity if the type says one thing and it is not the right class).
Thoughts?
> [Event producers] Implement RM writing app lifecycle events to ATS
> ------------------------------------------------------------------
>
> Key: YARN-3044
> URL: https://issues.apache.org/jira/browse/YARN-3044
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Naganarasimha G R
> Attachments: YARN-3044.20150325-1.patch
>
>
> Per design in YARN-2928, implement RM writing app lifecycle events to ATS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
