[
https://issues.apache.org/jira/browse/PIG-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488901#comment-13488901
]
Cheolsoo Park commented on PIG-3021:
------------------------------------
Hi Chang,
I think that the current behavior of OTHERWISE is from that we translate it to
a "FILTER BY NOT (expr)", and I am open to discussion about whether this is
good or bad.
But it is tricky to to change this because it is backward incompatible. Some
people may rely on the current behavior, so if we change semantics, their
scripts have to be modified. Therefore, we should change it only if there are
more benefits than inconveniences by introducing a backward incompatibility.
Nevertheless, I am happy to listen to other opinions.
Thanks!
> 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
