[
https://issues.apache.org/jira/browse/CALCITE-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584750#comment-16584750
]
Volodymyr Vysotskyi commented on CALCITE-2440:
----------------------------------------------
[~suez1224], thanks for the clarification. I'm wondering, will this query pass
if you change the alias for unnest result:
{code:sql}
SELECT a, s FROM T, UNNEST(T.c) as AAA(s)
SELECT T.a, AAA.s FROM T, UNNEST(T.c) as AAA(s)
{code}
There is no direct unit test for this problem, but the side effect of this
change may be observed in this line:
[https://github.com/apache/calcite/commit/68ba411e23ba930bb2086bb3eed4c46edfac23eb#diff-337728f1a3a35c634362df7a0a509505R4546].
Regarding unit tests with volcano planner, you may use a test from the
description of CALCITE-2223 as an example. You just should specify rules which
should be applied, and perhaps more {{EnumerableRules}}, since the initial
query was much simpler. Also, there is built rel nodes tree manually, but you
can use {{SqlToRelConverter}} to specify a query only.
> SQL with UNNEST fail in volcano planner in some cases
> -----------------------------------------------------
>
> Key: CALCITE-2440
> URL: https://issues.apache.org/jira/browse/CALCITE-2440
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.17.0
> Reporter: Shuyi Chen
> Assignee: Julian Hyde
> Priority: Major
>
> After [CALCITE-2291|https://issues.apache.org/jira/browse/CALCITE-2291],
> specifically, [this
> line|https://github.com/apache/calcite/blob/7088dc7261d294b7c6d5c9f4463435e95f0b9c15/core/src/main/java/org/apache/calcite/sql2rel/SqlToRelConverter.java#L1952]
> causes volcano planner to fail to find the best plan for query
> {code:java}
> SELECT a, s FROM T, UNNEST(T.c) as A (s)
> {code}
> . I'll try to write a unittest in Calcite to reproduce. [~cshi] [~vvysotskyi]
> [~HanumathRao], can you provide some context? Thanks a lot.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
