[ 
https://issues.apache.org/jira/browse/FLINK-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886023#comment-16886023
 ] 

Danny Chan commented on FLINK-13150:
------------------------------------

Actually we have an internal discussion with [~phoenixjiangnan], for 
TableEnvironment#registerTableSource and TableEnvironment#registerTableSink we 
did only register to the builtin catalog/database now( I change the name to 
builtin in FLINK-13209 ), one reason is that this tableSource/sink table are 
very kindly not serializable, non-like the CatalogTable.

Now for the tableSource/tableSink, we wrap is as a ConnectorCatalogTable, which 
i think is the root cause for serialization problem.

Ideally, all the table registered in should be serializable, including the scan 
table or scan + query (the view), we should and could have a serializable and 
unified Abstraction when register the table into the Catalog.

Only after that ,we can switch the catalog, and always register the table into 
current catalog(except that use specify the table path explicitly).

What we need is a discussion about the unifying of table sources/sinks and 
catalogTable, and i'm glad to take this, but this needs time, expect we can 
solve this problem in release 1.10




> defaultCatalogName and defaultDatabaseName in TableEnvImpl is not updated 
> after they are updated in TableEnvironment
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-13150
>                 URL: https://issues.apache.org/jira/browse/FLINK-13150
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>    Affects Versions: 1.9.0
>            Reporter: Jeff Zhang
>            Assignee: Danny Chan
>            Priority: Major
>
> defaultCatalogName and defaultDatabaseName in TableEnvImpl are initialized 
> when it is created and never changed even when they are updated in 
> TableEnvironment.
> The will cause issues that we may register table to the wrong catalog after 
> we changed the defaultCatalogName and defaultDatabaseName 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to