[
https://issues.apache.org/jira/browse/CALCITE-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17982757#comment-17982757
]
Mihai Budiu commented on CALCITE-7058:
--------------------------------------
It's a tradeoff: the time you spend cleaning up Jira could be spent fixing bugs.
I think it's worthwhile only if in this way you will find bugs that need to be
fixed and you plan to work solving them.
Detecting duplicate issues and closing them is not a goal in itself from my pov.
> 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)
