[
https://issues.apache.org/jira/browse/FLINK-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855095#comment-16855095
]
Bowen Li commented on FLINK-12626:
----------------------------------
[~twalthr] by taking a look at the
{{TableEnvImpl.registerTableSourceInternal()}}, I think it should solve this
JIRA. I will do a followup testing and add unit tests after FLINK-12604 is
merged.
> Client should not register table-source-sink twice in TableEnvironment
> ----------------------------------------------------------------------
>
> Key: FLINK-12626
> URL: https://issues.apache.org/jira/browse/FLINK-12626
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Client
> Reporter: Bowen Li
> Priority: Major
> Fix For: 1.9.0
>
>
> Currently for a table specified in SQL CLI yaml file, if it's with type:
> source-sink-table, it will be registered twice (as source and as sink) to
> TableEnv.
> As we've moved table management in TableEnv to Catalogs which doesn't allow
> registering dup named table, we need to come up with a solution to fix this
> problem.
> cc [~xuefuz] [~tiwalter] [~dawidwys]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
