[jira] [Commented] (DRILL-7345) Strange Behavior for UDFs with ComplexWriter Output

["Igor Guzenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-7345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905362#comment-16905362 ] 

Igor Guzenko commented on DRILL-7345:
-------------------------------------

Hi [~cgivre], could you please check that the issue is not caused by changes which was added as part of DRILL-6810 ? [Here|https://github.com/apache/drill/blob/85c77134d5d1bb9f96a5417036cccfb263ae8ae7/exec/java-exec/src/main/java/org/apache/drill/exec/expr/annotations/FunctionTemplate.java#L150] in javadoc described some limitations related to ComplexWriter output. 

> Strange Behavior for UDFs with ComplexWriter Output
> ---------------------------------------------------
>
>                 Key: DRILL-7345
>                 URL: https://issues.apache.org/jira/browse/DRILL-7345
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.17.0
>            Reporter: Charles Givre
>            Priority: Minor
>
> I wrote some UDFs recently and noticed some strange behavior when debugging them. 
> This behavior only occurs when there is ComplexWriter as output.  
> Basically, if the input to the UDF is nullable, Drill doesn't recognize the UDF at all.  I've found that the only way to get Drill to recognize UDFs that have ComplexWriters as output is:
> * Use a non-nullable holder as input
> * Remove the null setting completely from the function parameters.
> This approach has a drawback in that if the function receives a null value, it will throw an error and halt execution.  My preference would be to allow null handling, but I've not figured out how to make that happen.
> Note:  This behavior ONLY occurs when using a ComplexWriter as output.  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)