[
https://issues.apache.org/jira/browse/CALCITE-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17979823#comment-17979823
]
Mihai Budiu commented on CALCITE-7058:
--------------------------------------
Decorrelation produced a relation with a different type; before:
RecordType(INTEGER col1, DOUBLE col2, BOOLEAN col3, VARCHAR col4, INTEGER col5,
DECIMAL(6, 2) col6, INTEGER EXPR$0, INTEGER EXPR$00) after: RecordType(INTEGER
col1, DOUBLE col2, BOOLEAN col3, VARCHAR col4, INTEGER col5, DECIMAL(6, 2)
col6, INTEGER EXPR$0, INTEGER EXPR$07)
In this case a compiler-named column has been renamed. But the decorrelator in
general has no way of knowing which column names are compiler-generated.
> 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)
