[
https://issues.apache.org/jira/browse/PIG-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488889#comment-13488889
]
Chang Luo commented on PIG-3021:
--------------------------------
Hi Cheolsoo,
Thanks for the quick response. NULL is very tricky as in the SQL world. I can
understand your arguments for expected behavior. However, I don't think this
semantic is intuitive. When a user use OTHERWISE to define default collection,
he expects the default collection is a "catch all" collection.
In the above example, if x or y is null, it will fail the condition x==y and
users expect it goes to the default collection defined by OTHERWISE.
> Split results missing records when there is null values in the column
> comparison
> --------------------------------------------------------------------------------
>
> Key: PIG-3021
> URL: https://issues.apache.org/jira/browse/PIG-3021
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Chang Luo
>
> Suppose a(x, y)
> split a into b if x==y, c otherwise;
> One will expect the union of b and c will be a. However, if x or y is null,
> the record won't appear in either b or c.
> To workaround this, I have to change to the following:
> split a into b if x is not null and y is not null and x==y, c otherwise;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
