Hadoop QA commented on PIG-927:
-1 overall. Here are the results of testing the latest attachment
against trunk revision 825393.
+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
+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.
This message is automatically generated.
> null should be handled consistently in Join
> Key: PIG-927
> URL: https://issues.apache.org/jira/browse/PIG-927
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Pradeep Kamath
> Assignee: Daniel Dai
> Fix For: 0.6.0
> Attachments: PIG-927-1.patch
> Currenlty Pig mostly follows SQL semantics for handling null. However there
> are certain cases where pig may need to handle nulls correctly. One example
> is the join - joins on single keys results in null keys not matching to
> produce an output. However if the join is on >1 keys, in the key tuple, if
> one of the values is null, it still matches with another key tuple which has
> a null for that value. We need to decide the right semantics here.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.