Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 10 Feb 2011 00:16:58 +0000 (UTC)
From: "Tom White (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <724724700.6770.1297297018321.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (MAPREDUCE-1921) IOExceptions should contain the
 filename of the broken input files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom White commented on MAPREDUCE-1921:
--------------------------------------

We could make this slightly more general by not restricting to FileSplit. By using InputSplit's toString() method we get more information for FileSplit (path plus offset and length), and it works for other InputSplit implementations too.

> IOExceptions should contain the filename of the broken input files
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1921
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1921
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Krishna Ramachandran
>            Assignee: Krishna Ramachandran
>         Attachments: mapred-1921-1.patch, mapred-1921-3.patch, mapreduce-1921.patch
>
>
> If bzip or other decompression fails, the IOException  does not contain the name of the broken file that caused the exception.
> It would be nice if such actions could be avoided in the future by having the name of the files that are broken spelled
> out in the exception. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira