You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Prateek Vaishnav (JIRA)" <ji...@apache.org> on 2016/04/06 09:14:25 UTC

[jira] [Commented] (PIG-4680) Enable pig job graphs to resume from last successful state

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

Prateek Vaishnav commented on PIG-4680:
---------------------------------------

A gentle reminder [~rohini]

> Enable pig job graphs to resume from last successful state
> ----------------------------------------------------------
>
>                 Key: PIG-4680
>                 URL: https://issues.apache.org/jira/browse/PIG-4680
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>            Reporter: Abhishek Agarwal
>            Assignee: Prateek Vaishnav
>         Attachments: PIG-4680.patch, patch_recover
>
>
> Pig scripts can have multiple ETL jobs in the DAG which may take hours to finish. In case of transient errors, the job fails. When the job is rerun, all the nodes in Job graph will rerun. Some of these nodes may have already run successfully. Redundant runs lead to wastage of cluster capacity and pipeline delays. 
> In case of failure, we can persist the graph state. In next run, only the failed nodes and their successors will rerun. This is of course subject to preconditions such as 
>  - Pig script has not changed
>  - Input locations have not changed
>  - Output data from previous run is intact
>  - Configuration has not changed



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