hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick King (JIRA)" <j...@apache.org>
Subject [jira] Commented: (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
Date Fri, 05 Feb 2010 19:20:28 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830241#action_12830241
] 

Dick King commented on MAPREDUCE-1309:
--------------------------------------

The new javac warnings are uses of deprecated API in the test cases.  It's necessary at this
time.

The javadoc warnings look like this:

{noformat}

     [exec]   [javadoc] Building tree for all the packages and classes...
     [exec]   [javadoc] /grid/0/hudson/hudson-slave/workspace/Mapreduce-Patch-h6.grid.sp2.yahoo.net/trunk/src/java/org/apache/hadoop/mapred
                            /FileInputFormat.java:323: warning - @param argument "inputs"
is not a parameter name.
     [exec]   [javadoc] /grid/0/hudson/hudson-slave/workspace/Mapreduce-Patch-h6.grid.sp2.yahoo.net/trunk/src/java/org/apache/hadoop/mapreduce/lib/input
                            /FileInputFormat.java:356: warning - @param argument "inputs"
is not a parameter name.

{noformat}

[I changed the formatting on the console printout excerpt to make it render better]

These are warnings that have nothing to do with this patch.

> 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
>         Attachments: demuxer-plus-concatenated-files--2009-12-21.patch, demuxer-plus-concatenated-files--2010-01-06.patch,
demuxer-plus-concatenated-files--2010-01-08-b.patch, demuxer-plus-concatenated-files--2010-01-08-c.patch,
demuxer-plus-concatenated-files--2010-01-08-d.patch, demuxer-plus-concatenated-files--2010-01-08.patch,
demuxer-plus-concatenated-files--2010-01-11.patch, mapreduce-1309--2009-01-14-a.patch, mapreduce-1309--2009-01-14.patch,
mapreduce-1309--2010-01-20.patch, mapreduce-1309--2010-02-03.patch, mapreduce-1309--2010-02-04.patch
>
>
> 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.


Mime
View raw message