You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Volodymyr Vysotskyi (JIRA)" <ji...@apache.org> on 2019/08/13 08:59:00 UTC

[jira] [Updated] (DRILL-6810) Disable NULL_IF_NULL NullHandling for functions with ComplexWriter

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

Volodymyr Vysotskyi updated DRILL-6810:
---------------------------------------
    Labels: doc-impacting ready-to-commit  (was: ready-to-commit)

> Disable NULL_IF_NULL NullHandling for functions with ComplexWriter
> ------------------------------------------------------------------
>
>                 Key: DRILL-6810
>                 URL: https://issues.apache.org/jira/browse/DRILL-6810
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.14.0
>            Reporter: Bohdan Kazydub
>            Assignee: Bohdan Kazydub
>            Priority: Major
>              Labels: doc-impacting, ready-to-commit
>             Fix For: 1.15.0
>
>
> Currently NullHandling.NULL_IF_NULL is allowed for UDFs with @Output of type org.apache.drill.exec.vector.complex.writer.BaseWriter.ComplexWriter but no null handling is performed for the kind of functions which leads to confusion. The problem is ComplexWriter holds list/map values and Drill does not yet support NULL values for the types (there is an issue to allow null maps/lists in [DRILL-4824|https://issues.apache.org/jira/browse/DRILL-4824]).
> For such functions support for NULL_IF_NULL will be disabled, as it is done for aggregate functions, and NullHandling.INTERNAL should be used instead.



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