[
https://issues.apache.org/jira/browse/CALCITE-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Budiu resolved CALCITE-6534.
----------------------------------
Fix Version/s: 1.38.0
Resolution: Fixed
Fixed in
[https://github.com/apache/calcite/commit/906a17f40f00550e3347b3459c7c2de7e439b3c2]
Thank you for the contribution, [~suibianwanwan33]
> Adjust type when pulling up Calc in JoinUnifyRule
> -------------------------------------------------
>
> Key: CALCITE-6534
> URL: https://issues.apache.org/jira/browse/CALCITE-6534
> Project: Calcite
> Issue Type: Improvement
> Reporter: suibianwanwan
> Assignee: suibianwanwan
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.38.0
>
>
> In JoinOnLeftCalcUnifyRule, JoinOnRIghtCalcUnifyRule, JoinOnCalcUnifyRule,
> calcite tries to pull up the calc operator to make Query equivalent to target
> . In CALCITE-6501, for the case where the assert is due to a difference in
> nullablity, we do an early intercept and return null. This will result in
> some cases that can be rewritten not being able to be rewritten.
> Therefore, We can adjust the nullability of the type if this rewrite
> maintains semantics. if RexNode satisfies null-if-null, we will adjust the
> nullability, if not, we should reject this rewrite regardless of the
> nullablility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
