[
https://issues.apache.org/jira/browse/FLINK-10553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-10553.
--------------------------------
Resolution: Won't Fix
Legacy planner will not be maintained anymore. Blink planner supports catalogs.
> Unified sink and source table name in SQL statement
> ---------------------------------------------------
>
> Key: FLINK-10553
> URL: https://issues.apache.org/jira/browse/FLINK-10553
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Legacy Planner
> Affects Versions: 1.6.0, 1.7.0
> Reporter: wangsan
> Priority: Major
> Labels: auto-unassigned, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Since sink table can now be registered using ExternalCatalog, just the same
> as source table, the source and sink name in SQL statement should also be
> treated equally. Now we can only use `catalog.database.table` for sink table
> (enclosed in back-ticks as a identifier), this is not consistent with source
> table name (do not treat the whole name as a identifier).
> *INSERT INTO catalog.database.sinktable SELECT ... FROM
> catalog.database.sourcetable* should be supported .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
