TsReaper opened a new pull request #9328: [FLINK-13521][sql-client] Allow 
setting configurations in SQL CLI
URL: https://github.com/apache/flink/pull/9328
 
 
   ## What is the purpose of the change
   
   Currently, we provide a set of configurations in blink planner to support 
optimization or enable some advanced feature. However, all the configurations 
can't be set in SQL CLI.
   
   This PR allows setting table environment configurations in SQL CLI by using 
the following methods:
   
   * Modify config files:
   ```yaml
   configuration:
     table:
       exec:
         spill-compression:
           enabled: true
           block-size: 128kb
       optimizer:
         join-reorder-enabled: true
   ```
   * Or use `set` command:
   ```
   SET table.exec.spill-compression.enable=true;
   SET table.exec.spill-compression.block-size=128kb;
   SET table.optimizer.join-reorder-enabled=true;
   ```
   
   Note that different from other options in SQL CLI, the `SET` command about 
table environment configurations does not start with `configuration.` prefix 
but directly uses the option name.
   
   ## Brief change log
   
    - Allow setting configurations in SQL CLI
   
   ## Verifying this change
   
   This change added tests and can be verified as follows: run the newly added 
tests `LocalExecutorITCase::testTableEnvConfigurations` and 
`ExecutionContextTest::testConfigurations`.
   
   ## 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? docs
   

----------------------------------------------------------------
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

Reply via email to