hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7590) Mavenize streaming and MR examples
Date Fri, 18 Nov 2011 16:32:52 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152949#comment-13152949
] 

Alejandro Abdelnur commented on HADOOP-7590:
--------------------------------------------

This patch takes care of build/testing of streaming.

My take on why we need a different JIRA for packaging and execution is:

Packaging ought to be done done using an assembly, the problem here is that streaming depends
on MR thus it cannot be added as dependency to MR. Because of this we need to do an assembly
module for tools and then stitch it in hadoop-dist with the others. (<rant>IMO we shouldn't
have dual artifact modules as we have today, that would simplify the assembly of everything</rant>)


                
> Mavenize streaming and MR examples
> ----------------------------------
>
>                 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, 0.24.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.23.1
>
>         Attachments: HADOOP-7590v1.patch, HADOOP-7590v1.sh, HADOOP-7590v2.patch, HADOOP-7590v2.sh,
HADOOP-7590v3.patch, HADOOP-7590v3.sh, HADOOP-7590v4.patch, HADOOP-7590v4.sh, HADOOP-7590v5.patch,
HADOOP-7590v5.sh, HADOOP-7590v6.patch, HADOOP-7590v6.sh, HADOOP-7590v7.patch, HADOOP-7590v7.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message