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

Ruben Q L resolved CALCITE-6642.
--------------------------------
    Resolution: Fixed

Fixed via 
[{{add1f8b}}|https://github.com/apache/calcite/commit/add1f8b8dac86bfbd8a9de5169baa97347119256]
 

Thanks [~cbrisson] for the patch!

> AggregateUnionTransposeRule should account for changes in nullability of 
> pushed down aggregates
> -----------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-6642
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6642
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.38.0
>            Reporter: Claude Brisson
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.39.0
>
>
> This bug affects {{AggregateUnionTransposeRule}}.
> When pushing down aggregate calls through unions, since the nullability of 
> the aggregated columns may differ from one union branch to another, the 
> expected nullability of the children aggregates in each union branch may 
> differ from the original aggregates.
> When assertions are enabled, this does provoke a failure when the new 
> aggregate relations do check whether the declared type and the expected type 
> are the same.



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

Reply via email to