[
https://issues.apache.org/jira/browse/CALCITE-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Budiu resolved CALCITE-7776.
----------------------------------
Fix Version/s: 1.43.0
Assignee: Jerome Isaac Haltom
Resolution: Fixed
Fixed in
[https://github.com/apache/calcite/commit/26e16dcc856976078dcaaf4cb0e47093a87696bd]
Thank you for the fix [~jhaltom]
> UNNEST WITH ORDINALITY over a column of type ANY has no ORDINALITY column
> -------------------------------------------------------------------------
>
> Key: CALCITE-7776
> URL: https://issues.apache.org/jira/browse/CALCITE-7776
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.42.0
> Reporter: Jerome Isaac Haltom
> Assignee: Jerome Isaac Haltom
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.43.0
>
>
> UNNEST of a column declared ANY ignores WITH ORDINALITY. The row type has a
> single column, so there is no ordinal to select, and naming two aliases fails
> validation.
> Given a table {{s.docs}} with columns {{ID}} INTEGER and {{TAGS}} ANY:
> {code:sql}
> select "D"."ID", "T"."X", "T"."O"
> from "s"."docs" as "D", UNNEST("D"."TAGS") WITH ORDINALITY as "T"("X", "O")
> {code}
> {noformat}
> org.apache.calcite.sql.validate.SqlValidatorException: List of column aliases
> must have same degree as table; table has 1 columns ('$unnest'), whereas
> alias list has 2 columns
> {noformat}
> The same query over a declared array gives both columns:
> {code:sql}
> select * from UNNEST(ARRAY['red', 'green']) WITH ORDINALITY as "T"("X", "O")
> {code}
> {noformat}
> X, O
> red|1
> green|2
> {noformat}
> The ANY branch of {{SqlUnnestOperator.inferReturnType}} returns before the
> block that adds the ORDINALITY column. {{Uncollect.deriveUncollectRowType}}
> does the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
