[
https://issues.apache.org/jira/browse/MAPREDUCE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-5933:
-------------------------------------
Attachment: MAPREDUCE-5933.patch
Updated patch addresses your comments.
Two questions though:
1. I'm not sure we should make the entity type in ALL_CAPS because then the
REST API requires ALL_CAPS (e.g.
{{http://localhost:8188/ws/v1/timeline/MAPREDUCE_JOB}}). Alternatively, the
REST API should be case insensitive (though that would be a separate JIRA)
2. All of the task-related events except for {{TaskUpdatedEvent}} have a
{{getTaskType()}} method so I can tell if it's a MAP or REDUCE task. Are you
aware of any reason for that or if it's just an oversight and I should fix it?
> Enable MR AM to post history events to the timeline server
> ----------------------------------------------------------
>
> Key: MAPREDUCE-5933
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5933
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mr-am
> Reporter: Zhijie Shen
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-5933.patch, MAPREDUCE-5933.patch,
> MAPREDUCE-5933.patch, MAPREDUCE-5933.patch, MAPREDUCE-5933.patch,
> mr_timelineserver_response.txt
>
>
> Nowadays, MR AM collects the history events and writes it to HDFS for JHS to
> source. With the timeline server, MR AM can put these events there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
