[
https://issues.apache.org/jira/browse/MAHOUT-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tom pierce updated MAHOUT-946:
------------------------------
Attachment: MAHOUT-946.patch
I thought about this some more and realized in many cases you might want
opposite behavior (delete the intermediate files unless something broke - in
that case save them for analysis).
In the end, I added a way to accumulate a list of Paths and clean those paths
at the end of processing, but left accumulation and triggering deletion as
subclass responsibilities.
> 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, 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
