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

Posted to issues@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2026/02/19 16:10:00 UTC

[jira] [Resolved] (IMPALA-14422) Calcite planner: Crash on Union with underlying Project and Values nodes

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

Michael Smith resolved IMPALA-14422.
------------------------------------
    Fix Version/s: Impala 5.0.0
       Resolution: Fixed

> Calcite planner: Crash on Union with underlying Project and Values nodes
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-14422
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14422
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Steve Carlin
>            Priority: Major
>             Fix For: Impala 5.0.0
>
>
> In version 1.37, for the query 
> select 1 union all select 5000
> Calcite was creating the following RelNode structure:
> LogicalUnion
>   LogicalValues (1), (5000)
> Calcite changed the behavior in 1.40 to ensure that all datatypes are matching.  Now it produces:
> LogicalUnion
>   LogicalProject(CAST 1 as SMALLINT)
>    LogicalValues 
>   LogicalProject(CAST 5000 as SMALLINT)
>    LogicalValues
> The introduction of the Project between Values exposed a bug in the ImpalaValuesRel class.



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