hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Dai (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-927) null should be handled consistently in Join
Date Wed, 21 Oct 2009 00:17:59 GMT

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

Daniel Dai commented on PIG-927:
--------------------------------

Hi, Alan,
Thank you for your comment. For the test case, if we do not have this patch, "1\t" for input1
will merge with "1\t" for input2, thus "join" will produce 2 output records. With this patch,
we can only see 1 output record.

> 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, PIG-927-2.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.


Mime
View raw message