[
https://issues.apache.org/jira/browse/CALCITE-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17979639#comment-17979639
]
suibianwanwan commented on CALCITE-7058:
----------------------------------------
Can you provide specific examples? Also, as discussed in many tickets, during
the planner, we generally don't guarantee that column names will be preserved,
So I think making the checks weaker is correct.
> 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)
