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 2013/12/17 22:34:07 UTC

[jira] [Commented] (TEZ-680) Events from tasks/vertices should not flow to dependents until after a commit.

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

Hitesh Shah commented on TEZ-680:
---------------------------------

However, there could be a potential option to send additional events to obsolete prior events. Not sure how this would work in case of committers that move the data to a different location. 

> Events from tasks/vertices should not flow to dependents until after a commit. 
> -------------------------------------------------------------------------------
>
>                 Key: TEZ-680
>                 URL: https://issues.apache.org/jira/browse/TEZ-680
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>
> Taking a use-case where an edge persists data in HDFS and the source vertex defines a committer, the destination vertex should not receive events pointing to the location of generated data until after the committer has been invoked.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)