[
https://issues.apache.org/jira/browse/TEZ-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated TEZ-646:
-------------------------------
Attachment: TEZ-646.3.txt
Thanks for the review. Patch addresses the comments (var name and removal of
the Composite base class). Also removes a bit from TezClientUtils which was
causing build failures (missing Nullable). Will commit it in a bit.
On the Events itself - I think some work is needed. There's code to check types
and explicitly cast between DataMovementEvents / InputFailedEvents all over
the place.
Maybe we need categories of Events, or interfaces like VersionedEvent just to
make access easier. Will open a separate jira.
> Avoid creating multiple copies of the same Event payload
> --------------------------------------------------------
>
> Key: TEZ-646
> URL: https://issues.apache.org/jira/browse/TEZ-646
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Priority: Critical
> Attachments: TEZ-646.1.txt, TEZ-646.2.txt, TEZ-646.3.txt
>
>
> OnFileSortedOutput generates the same event payload for all downstream tasks.
> As an example, for a simple MR job - the number of copies of this is equal to
> the number of reduce tasks.
> This needs to be done in a clean manner though - since the event model is
> meant to generate a separate payload for each downstream task.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
