You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2019/07/08 13:38:00 UTC

[jira] [Commented] (FLINK-13150) defaultCatalogName and defaultDatabaseName in TableEnvImpl is not updated after they are updated in TableEnvironment

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

Jeff Zhang commented on FLINK-13150:
------------------------------------

[~phoenixjiangnan] Could you help take a look at this issue ? 

> 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
>            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.3#76005)