[
https://issues.apache.org/jira/browse/FLINK-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887816#comment-16887816
]
Timo Walther commented on FLINK-13150:
--------------------------------------
Hi [~danny0405],
yes making table operations and expressions serializable should be targeted for
the 1.10 release. For types we already introduced a serializable string
representation, but the other classes such as
{{QueryOperation#asSerializableString}} throw an exception for now. We did not
want to rush on this topic because introducing serializability and persistence
might cause future backwards compatibility issues which is why the design must
be future proof.
Regarding the catalog terminology maybe I can clarify the terms: The
{{builtInCatalog}} that is specified in {{EnvironmentSettings}} is the
in-memory catalog that is always present in a table environment for now. It
cannot be changed within a session. Initially the {{currentCatalog}} is set to
the value of {{builtInCatalog}}. So it is always possible to register an
"anonymous" source/sink/function. In the future the {{builtInCatalog}} is not
necessary anymore once all objects are serializable. [~dawidwys] correct me if
my explanation contains errors.
> 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)
