Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <223122171.1261092378229.JavaMail.jira@brutus>
Date: Thu, 17 Dec 2009 23:26:18 +0000 (UTC)
From: "Dick King (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Created: (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
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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.