You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (Jira)" <ji...@apache.org> on 2019/11/04 12:44:00 UTC

[jira] [Updated] (DRILL-7366) Improve Null Handling for UDFs with Complex Output

     [ https://issues.apache.org/jira/browse/DRILL-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arina Ielchiieva updated DRILL-7366:
------------------------------------
    Fix Version/s:     (was: 1.17.0)
                   1.18.0

> Improve Null Handling for UDFs with Complex Output
> --------------------------------------------------
>
>                 Key: DRILL-7366
>                 URL: https://issues.apache.org/jira/browse/DRILL-7366
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.16.0
>            Reporter: Charles Givre
>            Priority: Major
>             Fix For: 1.18.0
>
>
> If there is a UDF which has a complex field (Map or List) as output, Drill does not allow the UDF to have nullable input and it creates additional complexity when writing these kinds of UDFs. 
> I therefore would like to propose that two options be added to the FunctionTemplate for null handling:  {{EMPTY_LIST_IF_NULL}}, and {{EMPTY_MAP_IF_NULL}} which, would simplify UDF creation.  I'm envisioning that if either of these options were selected, and the UDF receives any null value as input, the UDF will return either an empty map or list. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)