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

Hudson commented on MAPREDUCE-3993:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2454 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2454/])
    MAPREDUCE-3993. Graceful handling of codec errors during decompression 
(kkambatl via tucu) (Revision 1359345)

     Result = FAILURE
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1359345
Files : 
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/IOUtils.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/TestIOUtils.java
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/IFile.java

                
> Graceful handling of codec errors during decompression
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-3993
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3993
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv1, mrv2
>    Affects Versions: 0.23.1, 1.0.2
>            Reporter: Todd Lipcon
>            Assignee: Karthik Kambatla
>             Fix For: 1.2.0, 2.0.1-alpha
>
>         Attachments: MR-3993_branch1.patch, MR-3993_branch1.patch, 
> MR-3993_trunk.patch, MR-3993_trunk.patch
>
>
> When using a compression codec for intermediate compression, some cases of 
> corrupt data can cause the codec to throw exceptions other than IOException 
> (eg java.lang.InternalError). This will currently cause the whole reduce task 
> to fail, instead of simply treating it like another case of a failed fetch.

--
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

        

Reply via email to