dawidwys opened a new pull request #10223:  [FLINK-14787][configuration] Add 
configure method to StreamExecutionEnvironment
URL: https://github.com/apache/flink/pull/10223
 
 
   ## What is the purpose of the change
   
   This PR adds ability to configure StreamExecutionEnvironment from 
ReadableConfig
   
   It is based on #10222 
   
   ## Brief change log
   
   - Added necessary ConfigOptions
   - Added possibility to configure StreamExecutionEnvironment from 
ReadableConfig
   - Make the enum matching in Configuration more lenient in regards to case 
sensitivity (this is needed to match enums that do not follow enum naming 
convention e.g. `TimeCharacteristic`)
   - Regenerated corresponding documentation tables
   
   ## Verifying this change
   
   This change added tests:
   * StreamExecutionEnvironmentConfigurationTest
   * StreamExecutionEnvironmentComplexConfigurationTest
   
   ## 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:
[email protected]


With regards,
Apache Git Services

Reply via email to