[FLINK-13176] remember current catalog and database in SQL CLI SessionContext

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: Table SQL / Client
• Labels: pull-request-available
• Assignee: Bowen Li
• Reporter: Bowen Li
• Created: 09/Jul/19 19:38
• Updated: 01/Aug/19 10:57
• Resolved: 16/Jul/19 02:02

Description

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

Issue Links

• links to: GitHub Pull Request #9049