zjuwangg opened a new pull request #10296: [FLINK-14691][table]Add use/create/drop/alter database operation and support it in flink/blink planner URL: https://github.com/apache/flink/pull/10296 ## What is the purpose of the change According to FLIP-69, we should support such following DDLs related to the database in the TableEnvironment through `sqlUpdate()` method. 1. createDatabaseStatement: CREATE DATABASE [ IF NOT EXISTS ] [ catalogName.] dataBaseName [ COMMENT database_comment ] [WITH ( name=value [, name=value]*)] 2. dropDatabaseStatement: DROP DATABASE [ IF EXISTS ] [ catalogName.] dataBaseName [ (RESTRICT|CASCADE)] 3. alterDatabaseStatement: ALTER DATABASE [ catalogName.] dataBaseName SET ( name=value [, name=value]*) 4. useDatabaseStatement: USE [ catalogName.] dataBaseName ## Brief change log - [9c6174e](https://github.com/apache/flink/commit/9c6174ed579f803616f3fce54782eb541a05223a)add use database support in tableEnvironment - [37ef49f](https://github.com/apache/flink/commit/37ef49faee99f3e52c95fd3087a9ae8027920bee)add create database support in tableEnvironment - [e1b42d8](https://github.com/apache/flink/commit/e1b42d810cc158f8716208c3501be391efd910ce)add drop database support in tableEnvironment - [7c5e46d](https://github.com/apache/flink/commit/7c5e46d1f794cb01be5088f5f5d29aec5850bf7f)add alter database support in tableEnvironment ## Verifying this change This change added tests and can be verified as follows: - *SqlToOperationConverterTest#testUseDatabase* and *CatalogTableITCase#testUseDatabase* - *SqlToOperationConverterTest#testCreateDatabase* and *CatalogTableITCase#testCreateDatabase* - *SqlToOperationConverterTest#testDropDatabase* and *CatalogTableITCase#testDropDatabase* - *SqlToOperationConverterTest#testAlterDatabase* and *CatalogTableITCase#testAlterDatabase* ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): ( no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (yes ) - If yes, how is the feature documented? (not applicable)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
