crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CRUNCH-217) Crunch PipelineResult objects do not capture failures
Date Mon, 10 Jun 2013 16:45:20 GMT

     [ https://issues.apache.org/jira/browse/CRUNCH-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Wills resolved CRUNCH-217.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7.0

Committed. Thanks Joe!
                
> Crunch PipelineResult objects do not capture failures
> -----------------------------------------------------
>
>                 Key: CRUNCH-217
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-217
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.0
>            Reporter: Joseph Adler
>            Assignee: Josh Wills
>             Fix For: 0.7.0
>
>         Attachments: CRUNCH-217.patch
>
>
> We use Crunch within Azkaban (a scheduling a and workflow tool, similar to Oozie). We
need to be able to run a crunch pipeline from within another Java program, then test for success
using code like this:
> {code}
>     PipelineResult mainResult = mainPipeline.run();
>     if (!mainResult.succeeded())
>     {
>         throw new Exception("Pipeline failed: " + mainPipeline.getName() + "\n");
>     }
>     return 0;
> {code}
> Currently, PipelineResult objects don't let you do this; the succeeded() method will
always return true. 
> I have enclosed a patch that addresses this issue for in-memory and map-reduce pipelines.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message