You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "duan xiong (Jira)" <ji...@apache.org> on 2021/08/16 00:38:00 UTC
[jira] [Assigned] (CALCITE-4729) Column in CTE should be ambiguous
[ https://issues.apache.org/jira/browse/CALCITE-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
duan xiong reassigned CALCITE-4729:
-----------------------------------
Assignee: duan xiong
> Column in CTE should be ambiguous
> ---------------------------------
>
> Key: CALCITE-4729
> URL: https://issues.apache.org/jira/browse/CALCITE-4729
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Lantao Jin
> Assignee: duan xiong
> Priority: Major
>
> {code}
> create table test (a int);
> with t as
> (
> select * from test t1 join test t2 on t1.a=t2.a
> )
> select t.a from t;
> {code}
> The above query fails with 't.a' is ambiguous in Spark/Presto/Postgres. But it succeeds in Calcite. Currently, many and many companies use Calcite as a query federation layer upon multiple query engines such as Spark and Presto. But this behavior confused users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)