You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 07:07:05 UTC

[jira] [Resolved] (MAPREDUCE-212) want InputFormat for task logs

     [ https://issues.apache.org/jira/browse/MAPREDUCE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-212.
----------------------------------------

    Resolution: Won't Fix

I'm going to close this as won't fix.  In some cases, Hadoop has slowly been moving log files over to avro.  In other cases, the logs are 3rd party/ecosystem controlled and could be in the format for that project.



> want InputFormat for task logs
> ------------------------------
>
>                 Key: MAPREDUCE-212
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-212
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Doug Cutting
>         Attachments: hadoop1199-v2.patch, hadoop1199.patch
>
>
> We should provide an InputFormat implementation that includes all the task logs from a job. Folks should be able to do something like:
> job = new JobConf();
> job.setInputFormatClass(TaskLogInputFormat.class);
> TaskLogInputFormat.setJobId(jobId);
> ...
> Tasks should ideally be localized to the node that each log is on.
> Examining logs should be as lightweight as possible, to facilitate debugging. It should not require a copy to HDFS. A faster debug loop is like a faster search engine: it makes people more productive. The sooner one can find that, e.g., most tasks failed with a NullPointerException on line 723, the better. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)