You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Tanner Clary (Jira)" <ji...@apache.org> on 2023/09/12 15:53:00 UTC

[jira] [Resolved] (CALCITE-5862) Incorrect semantics of ARRAY function (Spark library) when elements have Numeric and Character types

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

Tanner Clary resolved CALCITE-5862.
-----------------------------------
    Fix Version/s: 1.36.0
       Resolution: Fixed

> Incorrect semantics of ARRAY function (Spark library) when elements have Numeric and Character types
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-5862
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5862
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.34.0
>            Reporter: Ran Tao
>            Assignee: Ran Tao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.36.0
>
>
> when run select array(1, 2, 'Hi')
> spark-sql (default)> select array(1, 2, 'Hi');
> ["1","2","Hi"] 
> and calcite will cause {*}java.lang.NullPointerException: inferred array element type{*}.
> Spark supports both character and numeric types in the array, and the return type is character.
> In fact, calcite also allows both character and numeric types to exist in the operand type checker, but there is no corresponding processing logic in the return type inference, so an error is reported.
> We should fix this bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)