[
https://issues.apache.org/jira/browse/CALCITE-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555859#comment-17555859
]
Benchao Li commented on CALCITE-5127:
-------------------------------------
bq. However, many extensions of Filter, Project, etc., in downstream projects
are not really "physical" nodes but still "logical" with few or none additional
attributes.
[~zabetak] This is good addition, I didn't know that before.
I don't know if there is any downstream projects which requires we propagate
the correlated variables to the physical nodes, AFAIK, this should be a very
rare case.
Then put it all together, how about we put the correlated variables in the base
{{RelNode}} ({{Project}}/{{Filter}}), but we do not guarantee it's propagation
in the optimization phase? We can document this design in
{{RelNode#getVariablesSet}}.
What do you think?
> Error when executing query with subquery in select list that uses outer
> column of array type
> --------------------------------------------------------------------------------------------
>
> Key: CALCITE-5127
> URL: https://issues.apache.org/jira/browse/CALCITE-5127
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Dmitry Sysolyatin
> Assignee: Benchao Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.32.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following queries fail:
> {code}
> SELECT ARRAY(SELECT s.x) FROM (SELECT ARRAY[1,2,3] as x) s;
> SELECT ARRAY(SELECT * FROM UNNEST(s.x) y) FROM (SELECT ARRAY[1,2,3] as x) s;
> SELECT (SELECT CARDINALITY(s.x) LIMIT 1) FROM (SELECT ARRAY[1,2,3] as x) s;
>
> {code}
> With exception:
> {code}
> Caused by: java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.util.List
> {code}
> You can find test cases for this task in
> https://github.com/apache/calcite/commit/27e68ded2c3bea7d7af73dd1dc156e46fb3591a8
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
