hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7590) Mavenize the MR1 JARs (main and test) creation
Date Wed, 31 Aug 2011 05:35:09 GMT

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

Alejandro Abdelnur updated HADOOP-7590:
---------------------------------------

    Attachment: HADOOP-7590v2.patch
                HADOOP-7590v2.sh

v2 of the script/patch.

The layout is almost identical to what Mahadev suggested.

{code}
hadoop-mapreduce-project/hadoop-mapreduce-mr1/
                         hadoop-mapreduce-examples/
hadoop-tools/hadoop-mapreduce-tools/
{code}

I've run into a few quirks because of the code dependencies:

* Tweaked examples DistSum not to use JobTracker
* Examples tests stay in MR1
* Tools tests stay in MR1
* Rumen stays in MR1, it depend on MR1 stuff
* Old Discp and Logalizer stay in MR1, depend on MR1 stuff

All this is due to the fact that things are still using MR1 code.

IMO we can go with both v1 or v2, if v1 we can later move examples/tools out as testcases
are written using MR2 stuff.

> Mavenize the MR1 JARs (main and test) creation
> ----------------------------------------------
>
>                 Key: HADOOP-7590
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7590
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 0.23.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-7590v1.patch, HADOOP-7590v1.sh, HADOOP-7590v2.patch, HADOOP-7590v2.sh
>
>
> MR1 code is still available in MR2 for testing contribs.
> While this is a temporary until contribs tests are ported to MR2.
> As a follow up the contrib projects themselves should be mavenized.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message