[
https://issues.apache.org/jira/browse/PIG-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793428#action_12793428
]
Hadoop QA commented on PIG-1165:
--------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12428644/PIG-1165-1.patch
against trunk revision 892939.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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 passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/149/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/149/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/149/console
This message is automatically generated.
> Signature of loader does not set correctly for order by
> -------------------------------------------------------
>
> Key: PIG-1165
> URL: https://issues.apache.org/jira/browse/PIG-1165
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.6.0
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: 0.6.0
>
> Attachments: PIG-1165-1.patch
>
>
> In pig, we need to set signature for each LoadFunc. Currently, we use alias
> of the LOAD statement in Pig script of the signature of the LoadFunc. One use
> case we have is in LoadFunc, we use signature to retrieve pruned columns of
> each specific loader. However, in "order by" statement, we do not set
> signature for the loader correctly. In this case, we do not prune the loader
> correctly.
> For example, the following script produce wrong result:
> {code}
> a = load '1.txt' as (a0, a1);
> b = order a by a1;
> c = order b by a1;
> d = foreach c generate a1;
> dump d;
> {code}
> 1.txt:
> {code}
> 1 a
> 2 b
> 3 c
> 6 d
> 5 e
> {code}
> expected result:
> a
> b
> c
> d
> e
> current result:
> 1
> 2
> 3
> 5
> 6
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
