[
https://issues.apache.org/jira/browse/MAHOUT-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187369#comment-13187369
]
Lance Norskog edited comment on MAHOUT-946 at 1/17/12 1:47 AM:
---------------------------------------------------------------
Yup, you're right. Shell script should be a separate project.
One thing that jumps out at me is refactoring. The AbstractJob class is a
toolkit for common tasks. It has a lot of kit for maybe the first 1/3 of the
code to set up and run a job from the command line. Could it also have a "run
job and fail nicely" method?
was (Author: lancenorskog):
Yup, you're right. Shell script should be a separate project.
One thing that jumps out at me is refactoring. The AbstractJob class is a
toolkit for common tasks. Right not it has a lot of kit for maybe the first 1/3
of the code to set up and run a job from the command line. Could it also have
a "run job and fail nicely" method?
> Map-reduce job status often left unchecked
> ------------------------------------------
>
> Key: MAHOUT-946
> URL: https://issues.apache.org/jira/browse/MAHOUT-946
> Project: Mahout
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: tom pierce
> Attachments: MAHOUT-946.patch
>
>
> I've run into a few places in Mahout where mapreduce jobs can fail and their
> status won't be checked, so processing will continue on. This sometimes
> obscures the root problem. I've tracked down a bunch of places where this
> problem exists, and tried to fix the code to do something reasonable (return
> -1 status code, throw exception, etc.) when jobs fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
