[
https://issues.apache.org/jira/browse/PIG-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olga Natkovich updated PIG-781:
-------------------------------
Status: Open (was: Patch Available)
Gunther, thanks for the patch.
A couple of comments:
(1) It would be nice if the tests added to TestGrunt would touch a done file
and we would validate that it was/was not created depending on the test case.
This is what some of the users are doing and it would be nice to test that.
(2) As we discussed, all the output need to be going to a single log file on
the client.
(3) The patch did not pass the automatedt test. (See above). Lookks like it
needs to be regenerated with the latest code.
The rest looks good.
> 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.
