[
https://issues.apache.org/jira/browse/FLINK-11478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323378#comment-17323378
]
Flink Jira Bot commented on FLINK-11478:
----------------------------------------
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.
> Handle existing table registration via YAML file in the context of catalog
> support
> ----------------------------------------------------------------------------------
>
> Key: FLINK-11478
> URL: https://issues.apache.org/jira/browse/FLINK-11478
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API, Table SQL / Client
> Reporter: Xuefu Zhang
> Assignee: Xuefu Zhang
> Priority: Major
> Labels: stale-assigned
>
> Before we introduce Catalog, it's common for user to define his/her tables in
> SQL client YAML file. With catalog support, it is no longer necessary.
> However, to keep backward compatibility, this mechanism should continue
> functioning. Behind the scene, we need to solve the problem of the same
> tables is registered every time user launches SQL client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
