You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/04/07 22:25:15 UTC

[jira] [Commented] (TEZ-694) Remove task commit burden from user code

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

Bikas Saha commented on TEZ-694:
--------------------------------

Spoke to Hitesh offline. Lets go with 2 - creating abstract classes. Lets come back to this once TEZ-695 is done.

> Remove task commit burden from user code
> ----------------------------------------
>
>                 Key: TEZ-694
>                 URL: https://issues.apache.org/jira/browse/TEZ-694
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Mohammad Kamrul Islam
>
> Its easy to forget to add commit logic in the processor after the logic in the run() method is done. After that its hard to debug why the outputs are not appearing after the dag completes even though all the tasks have been completed successfully. Since commit is an operation that should happen after the processor completes, it cannot be delegated entirely to the outputs. We can either do it in the LIORuntimeTask after processor.run() completes or create and abstract base processor class that does this after the real run() method completes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)