[GitHub] [flink] dawidwys opened a new pull request #9976: [FLINK-14493][core] Introduce data types to ConfigOptions.

[GitBox <gi...@apache.org>]

dawidwys opened a new pull request #9976: [FLINK-14493][core] Introduce data types to ConfigOptions.
URL: https://github.com/apache/flink/pull/9976
 
 
   
   ## What is the purpose of the change
   
   Add additional supported types to `ConfigOption`s as discussed in FLIP-77:
   https://cwiki.apache.org/confluence/display/FLINK/FLIP-77%3A+Introduce+ConfigOptions+with+Data+Types
   
   ## Brief change log
   
     - Extended `OptionBuilder`
     - Added `ReadableConfig` & `WritableConfig` interfaces
     - Updated `Configuration` with the above mentioned interfaces
     - **IMPORTANT: changed the error handling when parsing config options. Exceptions are no longer silently swallowed.**
   
   
   ## Verifying this change
   
   This change added unit tests:
   * ConfigurationConversionsTest (migrated from ConfigurationTest)
   * ConfigurationParsingInvalidFormatsTest
   * ReadableWritableConfigurationTest
   * StructuredOptionsSplitterTest
   
   ## 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:
users@infra.apache.org


With regards,
Apache Git Services