[
https://issues.apache.org/jira/browse/CALCITE-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099587#comment-18099587
]
Mihai Budiu commented on CALCITE-7669:
--------------------------------------
While trying to fix this I have uncovered additional bugs in the implementation
of ROW types, so I have filed CALCITE-7677 and CALCITE-7678, which will
probably need to be solved first.
> Uncollect should support the Trino semantics of UNNEST
> ------------------------------------------------------
>
> Key: CALCITE-7669
> URL: https://issues.apache.org/jira/browse/CALCITE-7669
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.42.0
> Reporter: Mihai Budiu
> Assignee: Mihai Budiu
> Priority: Minor
> Labels: pull-request-available
>
> UNNEST has two different semantics with respect to ROW fields: expand them
> into separate columns (standard) or expand them into a single column (used
> e.g., in Trino).
> The current implementation should be enhanced to handle this latter case
> explicitly by representing this semantics in the UNCOLLECT operator and in
> it's Enumerable implementation.
> This was originally part of CALCITE-7608
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
