hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4737) Hadoop does not close output file / does not call Mapper.cleanup if exception in map
Date Fri, 12 Apr 2013 20:52:18 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630614#comment-13630614
] 

Arun C Murthy commented on MAPREDUCE-4737:
------------------------------------------

Agree with [~tomwhite] - we'll need to mark this as incompatible even though it's actually
making behaviour consistent with o.a.h.mapred.

----

[~daijy] Can you please go ahead and add a test case for this? Thanks!
                
>  Hadoop does not close output file / does not call Mapper.cleanup if exception in map
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4737
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4737
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1-win
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>         Attachments: HADOOP-23-2.patch, 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

Mime
View raw message