dawidwys opened a new pull request #10431:  [FLINK-15067][table] Pass 
configuration to the underlying ExecutionEnvironment from TableEnvironment
URL: https://github.com/apache/flink/pull/10431
 
 
   ## What is the purpose of the change
   
   After this PR the `TableEnvironment` passes configuration to the underlying 
`StreamExecutionEnvironment`. It allows configuring options such as e.g. 
autoWatermarkInterval, globalJobParameters etc.
   
   It is possible to do it as follows:
   
   ```
   StreamExecutionEnvironment env = 
StreamExecutionEnvironment.getExecutionEnvironment();
   StreamTableEnvironment tEnv = StreamTableEnvironment.create(env);
        tEnv.getConfig().addConfiguration(
                new Configuration()
                        .set(CoreOptions.DEFAULT_PARALLELISM, 128)
                        .set(PipelineOptions.AUTO_WATERMARK_INTERVAL, 
Duration.ofMillis(800))
                        
.set(ExecutionCheckpointingOptions.CHECKPOINTING_INTERVAL, 
Duration.ofSeconds(30))
        );
   ```
   
   ## Verifying this change
   Added tests for blink and flink planners
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (**yes** / no)
     - If yes, how is the feature documented? (not applicable / docs / 
**JavaDocs** / not documented)
   

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to