[
https://issues.apache.org/jira/browse/FLINK-24141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jocean.shi updated FLINK-24141:
-------------------------------
Description:
I have a catalog named "a" and a database named "b" and a table named "b". when
I want to use other table named "c" through "b.c" then in fact is used table
"b".
because the "a"."b" is the first defaultSchema in the
FlinkCalciteCatalogReader, frist step is found "a"."b"."b"."c", "a"."b"."b" is
exists.
. we need set empty is the first defaultSchema
was:
I have a catalog named "a" and a database named "b" and a table named "b". when
I want to use other table named "c" through "b.c" then in fact is used table
"b".
because the "a"."b" is the first defaultSchema in the FlinkCalciteCatalogReader
. we need set empty is the first defaultSchema
> table can't have the same name with database or catalog
> -------------------------------------------------------
>
> Key: FLINK-24141
> URL: https://issues.apache.org/jira/browse/FLINK-24141
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.10.0, 1.11.0, 1.12.0
> Reporter: jocean.shi
> Priority: Minor
>
> I have a catalog named "a" and a database named "b" and a table named "b".
> when I want to use other table named "c" through "b.c" then in fact is used
> table "b".
> because the "a"."b" is the first defaultSchema in the
> FlinkCalciteCatalogReader, frist step is found "a"."b"."b"."c", "a"."b"."b"
> is exists.
> . we need set empty is the first defaultSchema
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
