[ 
https://issues.apache.org/jira/browse/PIG-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777265#action_12777265
 ] 

Hadoop QA commented on PIG-1064:
--------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12424755/PIG-1064-2.patch
  against trunk revision 835499.

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

    +1 tests included.  The patch appears to include 12 new or modified tests.

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

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

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

    -1 core tests.  The patch failed core unit tests.

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

Test results: 
http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/153/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/153/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/153/console

This message is automatically generated.

> Behvaiour of COGROUP with and without schema when using "*" operator
> --------------------------------------------------------------------
>
>                 Key: PIG-1064
>                 URL: https://issues.apache.org/jira/browse/PIG-1064
>             Project: Pig
>          Issue Type: Bug
>          Components: impl
>    Affects Versions: 0.6.0
>            Reporter: Viraj Bhat
>            Assignee: Pradeep Kamath
>             Fix For: 0.6.0
>
>         Attachments: PIG-1064-2.patch, PIG-1064.patch
>
>
> I have 2 tab separated files, "1.txt" and "2.txt"
> $ cat 1.txt 
> ====================
> 1       2
> 2       3
> ====================
> $ cat 2.txt 
> 1       2
> 2       3
> I use COGROUP feature of Pig in the following way:
> $java -cp pig.jar:$HADOOP_HOME org.apache.pig.Main
> {code}
> grunt> A = load '1.txt';            
> grunt> B = load '2.txt' as (b0, b1);
> grunt> C = cogroup A by *, B by *;  
> {code}
> 2009-10-29 12:46:04,150 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
> 1012: Each COGroup input has to have the same number of inner plans
> Details at logfile: pig_1256845224752.log
> ==========================================================
> If I reverse, the order of the schema's
> {code}
> grunt> A = load '1.txt' as (a0, a1);
> grunt> B = load '2.txt';            
> grunt> C = cogroup A by *, B by *;  
> {code}
> 2009-10-29 12:49:27,869 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
> 1013: Grouping attributes can either be star (*) or a list of expressions, 
> but not both.
> Details at logfile: pig_1256845224752.log
> ==========================================================
> Now running without schema??
> {code}
> grunt> A = load '1.txt';            
> grunt> B = load '2.txt';            
> grunt> C = cogroup A by *, B by *;
> grunt> dump C; 
> {code}
> 2009-10-29 12:55:37,202 [main] INFO  
> org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully 
> stored result in: "file:/tmp/temp-319926700/tmp-1990275961"
> 2009-10-29 12:55:37,202 [main] INFO  
> org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records 
> written : 2
> 2009-10-29 12:55:37,202 [main] INFO  
> org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written 
> : 154
> 2009-10-29 12:55:37,202 [main] INFO  
> org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2009-10-29 12:55:37,202 [main] INFO  
> org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ((1,2),{(1,2)},{(1,2)})
> ((2,3),{(2,3)},{(2,3)})
> ==========================================================
> Is this a bug or a feature?
> Viraj

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

Reply via email to