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 "Dick King (JIRA)" <ji...@apache.org> on 2009/12/22 00:53:18 UTC
[jira] Assigned: (MAPREDUCE-1309) I want to change the rumen job
trace generator to use a more modular internal structure, to allow for more
input log formats
[ https://issues.apache.org/jira/browse/MAPREDUCE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dick King reassigned MAPREDUCE-1309:
------------------------------------
Assignee: Dick King
> I want to change the rumen job trace generator to use a more modular internal structure, to allow for more input log formats
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1309
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1309
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Dick King
> Assignee: Dick King
>
> There are two orthogonal questions to answer when processing a job tracker log: how will the logs and the xml configuration files be packaged, and in which release of hadoop map/reduce were the logs generated? The existing rumen only has a couple of answers to this question. The new engine will handle three answers to the version question: 0.18, 0.20 and current, and two answers to the packaging question: separate files with names derived from the job ID, and concatenated files with a header between sections [used for easier file interchange].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.