hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6342) Create a script to squash a common, hdfs, and mapreduce tarball into a single hadoop tarball
Date Fri, 05 Nov 2010 16:08:52 GMT

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

Hadoop QA commented on HADOOP-6342:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 1031422.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/66//console

This message is automatically generated.

> Create a script to squash a common, hdfs, and mapreduce tarball into a single hadoop
> --------------------------------------------------------------------------------------------
>                 Key: HADOOP-6342
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6342
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: build
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.21.1
>         Attachments: h-6342.patch, HADOOP-6342.2.patch, HADOOP-6342.patch, tar-munge,
> It would be convenient for the transition if we had a script to take a set of common,
hdfs, and mapreduce tarballs and merge them into a single tarball. This is intended just to
help users who don't want to transition to split projects for deployment immediately.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message