[
https://issues.apache.org/jira/browse/PIG-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cheolsoo Park updated PIG-3021:
-------------------------------
Attachment: PIG-3021-2.patch
All unit tests pass. I made some minor change in a new patch.
Btw, if we really don't want to break backward compatibility, we can introduce
an optional keyword like NULLABLE. For example,
{code}
SPLIT foo INTO x IF <cond>, y OTHERWISE [ NULLABLE ];
{code}
If NULLABLE is specified, nulls will be stored in y; otherwise, nulls will be
discarded.
Currently, I didn't implement this idea, but please let me know if you like it
more. It should be straightforward to implement it.
> 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
> Assignee: Cheolsoo Park
> Attachments: PIG-3021-2.patch, PIG-3021.patch
>
>
> 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
