[
https://issues.apache.org/jira/browse/PIG-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Graham updated PIG-2929:
-----------------------------
Status: Open (was: Patch Available)
+1 to Cheolsoo's comments. A null value passed to a concat could be seen as an
invalid record where a null result it warranted. Plus there's the backward
compatibility issue.
If you want a concat with the semantics you describe, I think a custom UDF is
the way go.
@Chealsoo, thanks for the documentation patch. Would you please make one minor
edit, which is to remove the *now* from the text. Comments should be
non-temporal.
{noformat}
The MIN function now ignores NULL values.
{noformat}
> CONCAT returns null when 1 items is null
> ----------------------------------------
>
> Key: PIG-2929
> URL: https://issues.apache.org/jira/browse/PIG-2929
> Project: Pig
> Issue Type: Bug
> Components: documentation, internal-udfs
> Affects Versions: 0.9.2, 0.9.1, 0.9.0
> Reporter: Nicholas Verbeck
> Assignee: Cheolsoo Park
> Fix For: 0.11
>
> Attachments: PIG-2929.patch
>
>
> Just stumbled upon this issue over the weekend. It appears the built-in
> CONCAT function will return null in the advent of 1 item in the Tuple being
> null. If this is as intended it would be nice if the docs made note of this.
> Otherwise it would be nice if nulls where just skipped and a proper string of
> what was left was returned. If all items are null then just return null in
> that case.
--
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
