[
https://issues.apache.org/jira/browse/FLINK-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885774#comment-16885774
]
Bowen Li commented on FLINK-13176:
----------------------------------
[~ykt836] sorry I just saw your comment.
I wouldn't call them "conflicts". Depending on how and where you plan to reuse
CatalogManager, this PR may not be needed anymore and can be reverted if
necessary
> remember current catalog and database in SQL CLI SessionContext
> ---------------------------------------------------------------
>
> Key: FLINK-13176
> URL: https://issues.apache.org/jira/browse/FLINK-13176
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Client
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0, 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> currently the EnvironmentInstance/TableEnvironment in SQL CLI is not reused,
> it's recreated for all SQL commands. The resulting problem is that we lost
> state of the user configured current catalog/database. We believe users
> should be able to run 'USE CATALOG/DATABASE xxx' to change their current
> catalog/database despite the ones set in yaml files.
> The core design was that the SQL Client "Gateway" is stateless and the SQL
> Client "CLI" knows everything that is required to submit a SQL job. So only
> one request is sent with all information necessary. `USE CATALOG/DATABASE
> xxx` should be executed in the CLI and stored in the CLI's session context.
> The session context has higher priority than the YAML file.
> For `USE CATALOG/DATABASE xxx` use case the current design should be
> sufficient as the `USE` would just modify an `execution` property in the
> session context
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
