[
https://issues.apache.org/jira/browse/CALCITE-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17981689#comment-17981689
]
suibianwanwan commented on CALCITE-7058:
----------------------------------------
I agree that it's difficult to replace RelDecorrelator with rules. The complex
decorrelation framework requires top-down context, which is challenging to
implement in a pattern-matching planner. To my knowledge, no other project has
successfully accomplished something similar.
As discussed in CALCITE-7031, IMO, RelDecorrelator's framework design is
sufficient to handle complex decorrelation scenarios. I prefer to fix the
remaining issues based on it and support more types of RelNode.
> Decorrelator may produce different column names
> -----------------------------------------------
>
> Key: CALCITE-7058
> URL: https://issues.apache.org/jira/browse/CALCITE-7058
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.40.0
> Reporter: Mihai Budiu
> Assignee: Mihai Budiu
> Priority: Minor
>
> In [CALCITE-7024] I have introduced an assertion (Litmus) check in the
> decorrelator that the output relation type is identical to the input relation
> type. This assertion is too strong, because the decorrelator sometimes
> produces different column names in the result.
> This may be a bug, but in the meantime it can be side-stepped by making the
> check a bit weaker: the types are identical up to column names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
