You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/10/09 09:54:03 UTC
[jira] [Commented] (HADOOP-8904) Hadoop does not close output file
/ does not call Mapper.cleanup if exception in map
[ https://issues.apache.org/jira/browse/HADOOP-8904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472207#comment-13472207 ]
Hadoop QA commented on HADOOP-8904:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12548375/HADOOP-8904-1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1588//console
This message is automatically generated.
> Hadoop does not close output file / does not call Mapper.cleanup if exception in map
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-8904
> URL: https://issues.apache.org/jira/browse/HADOOP-8904
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1-win
> Reporter: Daniel Dai
> Attachments: HADOOP-8904-1.patch
>
>
> Find this in Pig unit test TestStore under Windows. There are dangling files because map does not close the file when exception happens in map(). In Windows, Hadoop will not remove a file if it is not closed. This happens in reduce() as well.
--
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