[
https://issues.apache.org/jira/browse/MAPREDUCE-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473198#comment-13473198
]
Hudson commented on MAPREDUCE-3678:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #1191 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1191/])
MAPREDUCE-3678. The Map tasks logs should have the value of input split it
processed. Contributed by Harsh J. (harsh) (Revision 1396032)
Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1396032
Files :
* /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/MapTask.java
> The Map tasks logs should have the value of input split it processed
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3678
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3678
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, mrv2
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Bejoy KS
> Assignee: Harsh J
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-3678-branch-1.patch, MAPREDUCE-3678.patch
>
>
> It would be easier to debug some corner in tasks if we knew what was the
> input split processed by that task. Map reduce task tracker log should
> accommodate the same. Also in the jobdetails web UI, the split also should be
> displayed along with the Split Locations.
> Sample as
> Input Split
> hdfs://myserver:9000/userdata/sampleapp/inputdir/file1.csv - <split
> no>/<offset from beginning of file>
> This would be much beneficial to nail down some data quality issues in large
> data volume processing.
--
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
