You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2015/01/21 22:33:34 UTC

[jira] [Commented] (TEZ-1991) Introduce additional DataMovementEvent types

    [ https://issues.apache.org/jira/browse/TEZ-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286310#comment-14286310 ] 

Hitesh Shah commented on TEZ-1991:
----------------------------------

Why not just have additional fields in the existing class? 

> Introduce additional DataMovementEvent types
> --------------------------------------------
>
>                 Key: TEZ-1991
>                 URL: https://issues.apache.org/jira/browse/TEZ-1991
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>
> IncrementalDataMovementEvents and potentially a FinalDataMovementEvent. This is primarily for pipelined data transfer; these serve to reduce the data stored in the AM - as well as the events sent to consumers - consolidated events / latest event should be adequate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)