You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Daniel Dai (JIRA)" <ji...@apache.org> on 2009/10/15 18:28:31 UTC
[jira] Assigned: (PIG-927) null should be handled consistently in
Join
[ https://issues.apache.org/jira/browse/PIG-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dai reassigned PIG-927:
------------------------------
Assignee: Daniel Dai
> 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.3.0
> Reporter: Pradeep Kamath
> Assignee: Daniel Dai
> 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.