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 Wed, 24 Apr 2013 17:29:18 GMT

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

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

Thanks for the review Tom. 

bq. Arun, can you mark this as an incompatible change and add some documentation to the release
notes field.
Of course.
                
>  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, 2.0.3-alpha, 1.1.2
>            Reporter: Daniel Dai
>            Assignee: Arun C Murthy
>         Attachments: HADOOP-23-2.patch, HADOOP-8904-1.patch, MAPREDUCE-4737_branch1.patch,
MAPREDUCE-4737_branch1.patch, MAPREDUCE-4737.patch, MAPREDUCE-4737.patch, MAPREDUCE-4737.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