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

Hadoop QA commented on MAPREDUCE-987:
-------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12537142/MAPREDUCE-987_rev3.patch
  against trunk revision .

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

    +1 tests included.  The patch appears to include 2 new or modified test 
files.

    -1 javac.  The applied patch generated 2067 javac compiler warnings (more 
than the trunk's current 2066 warnings).

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed these unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
 hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site:

                  
org.apache.hadoop.mapreduce.lib.input.TestCombineFileInputFormat

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2625//testReport/
Javac warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2625//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2625//console

This message is automatically generated.
                
> Exposing MiniDFS and MiniMR clusters as a single process command-line
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-987
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-987
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: build, test
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>            Priority: Minor
>         Attachments: HDFS-621-0.20-patch, HDFS-621.patch, 
> MAPREDUCE-987.patch, MAPREDUCE-987.patch, MAPREDUCE-987_branch-1.0.patch, 
> MAPREDUCE-987_rev2.patch, MAPREDUCE-987_rev3.patch
>
>
> It's hard to test non-Java programs that rely on significant mapreduce 
> functionality.  The patch I'm proposing shortly will let you just type 
> "bin/hadoop jar hadoop-hdfs-hdfswithmr-test.jar minicluster" to start a 
> cluster (internally, it's using Mini{MR,HDFS}Cluster) with a specified number 
> of daemons, etc.  A test that checks how some external process interacts with 
> Hadoop might start minicluster as a subprocess, run through its thing, and 
> then simply kill the java subprocess.
> I've been using just such a system for a couple of weeks, and I like it.  
> It's significantly easier than developing a lot of scripts to start a 
> pseudo-distributed cluster, and then clean up after it.  I figure others 
> might find it useful as well.
> I'm at a bit of a loss as to where to put it in 0.21.  hdfs-with-mr tests 
> have all the required libraries, so I've put it there.  I could conceivably 
> split this into "minimr" and "minihdfs", but it's specifically the fact that 
> they're configured to talk to each other that I like about having them 
> together.  And one JVM is better than two for my test programs.

--
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

        

Reply via email to