[
https://issues.apache.org/jira/browse/FLINK-10553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323455#comment-17323455
]
Flink Jira Bot commented on FLINK-10553:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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 / API
> Affects Versions: 1.6.0, 1.7.0
> Reporter: wangsan
> Assignee: wangsan
> Priority: Major
> Labels: pull-request-available, stale-assigned
> 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)
