[
https://issues.apache.org/jira/browse/PIG-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499605#comment-13499605
]
Chang Luo commented on PIG-3021:
--------------------------------
I agree with the discussion about NULL. I also agreed CONCAT(null, something)
= null. My issue is on the OTHERWISE keyword not NULL. Maybe it only has
issues when NULL is involved but maybe there might be other cases where the
same confusion occurs.
I understand it's breaking change and ok with won't-fix. But if I were to
redesign SPLIT/OTHERWISE from beginning, I would make OTHERWISE a catch-all
default collection.
One suggestion is to give an explicit example of combination of NULL and
OTHERWISE keywords in the SPLIT documentation.
I can't post to the users mailing list. Could you please forward my comments
to that list? 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
