[
https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382343#comment-14382343
]
Naganarasimha G R commented on YARN-3044:
-----------------------------------------
[~sjlee0],
bq. I see. So your point is whether the storage implementation can recognize
different entity types and act accordingly? If so, the answer is yes. The
storage implementation can easily introspect the type of the entity and do the
right thing based on the type if needed.
Well if introspection is by checking through TimelineEntity.getType and then
cast it to the specific TimelineEntity, then it can break if the client/AM by
chance tries to post a normal TimelineEntity with type as
TimelineEntityType.YARN_APPLICATION or other system entities. Or other
approaches like checking with {{instance of}} or the likes sounds inappropriate.
> [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)
