[
https://issues.apache.org/jira/browse/PIG-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708752#action_12708752
]
Hadoop QA commented on PIG-781:
-------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12407727/partial_failure.patch
against trunk revision 774167.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 14 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-minerva.apache.org/37/console
This message is automatically generated.
> Error reporting for failed MR jobs
> ----------------------------------
>
> Key: PIG-781
> URL: https://issues.apache.org/jira/browse/PIG-781
> Project: Pig
> Issue Type: Improvement
> Reporter: Gunther Hagleitner
> Attachments: partial_failure.patch, partial_failure.patch
>
>
> If we have multiple MR jobs to run and some of them fail the behavior of the
> system is to not stop on the first failure but to keep going. That way jobs
> that do not depend on the failed job might still succeed.
> The question is to how best report this scenario to a user. How do we tell
> which jobs failed and which didn't?
> One way could be to tie jobs to stores and report which store locations won't
> have data and which ones do.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
