[
https://issues.apache.org/jira/browse/TEZ-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027287#comment-14027287
]
Bikas Saha commented on TEZ-1131:
---------------------------------
Composite events are actually translated to individual events for routing (and
share the payload to reduce memory). Thats existing functionality.
{code} private void handleCompositeDataMovementEvent(TezEvent tezEvent) {
CompositeDataMovementEvent compEvent = (CompositeDataMovementEvent)
tezEvent.getEvent();
EventMetaData srcInfo = tezEvent.getSourceInfo();
for (DataMovementEvent dmEvent : compEvent.getEvents()) {
TezEvent newEvent = new TezEvent(dmEvent, srcInfo);
sendTezEventToDestinationTasks(newEvent);
}
}{code}
Fixed rest of the comments.
> Simplify EdgeManager.routeDataMovementEventToDestination()
> ----------------------------------------------------------
>
> Key: TEZ-1131
> URL: https://issues.apache.org/jira/browse/TEZ-1131
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-1131.1.patch
>
>
> 2 pieces of feedback from [~daijy]
> 1) Its not clear the event.sourceIndex needs to be accessed. Solution - Make
> it part of the method parameters
> 2) the Map<InputIndex, List<TaskIndex>> is convoluted. Solution - Replace
> with Map<TaskIndex, InputIndex>. Amazing why we did not do this in the first
> place.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
