[
https://issues.apache.org/jira/browse/PIG-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575972#comment-13575972
]
Rohini Palaniswamy commented on PIG-3179:
-----------------------------------------
I meant something like this.
Input-split:
file=hdfs://gridx.yahoo.com:8020/tmp/bz-6086044/msh_grouped.bz2/part-r-00032.bz2,
start-offset=0,length=11814548
Each input split in a single line.
Question to folks - Is someone one parsing this log information? This is
something that can also be logged to a hdfs file apart from stderr of the map
task. Just asking to know whether this will cause any backward incompatibility
issues?
> Task Information Header only prints out the first split for each task
> ---------------------------------------------------------------------
>
> Key: PIG-3179
> URL: https://issues.apache.org/jira/browse/PIG-3179
> Project: Pig
> Issue Type: Improvement
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Priority: Trivial
> Attachments: pig-3179-v01.patch
>
>
> When a task's PigSplit is containing more than wrappedSplit, it only logs the
> first fileinfo.
> When debugging, I saw
> {noformat}
> ===== Task Information Header =====
> Command: bash ....
> Start time: Mon Feb 11 16:41:21 UTC 2013
> Input-split file: hdfs://abc.bcd.efg:8020/tmp/hij/part-r-00000.bz2
> Input-split start-offset: 0Input-split length: 11854247
> {noformat}
> but the actual error was happing while reading part-r-00007.bz2. It would
> have been nice if the log showed all the info that task was going to read.
--
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
