dawidwys opened a new pull request #11622: [FLINK-16913][configuration, 
statebackend] Migrated StateBackends to use ReadableConfig instead of 
Configuration
URL: https://github.com/apache/flink/pull/11622
 
 
   ## What is the purpose of the change
   
   StateBackendFactories do not need a full read and write access to the
   Configuration object. It's sufficient to have read only access. Moreover
   the ReadableConfig is a lightweight interface that can be implemented in
   other ways, not just through the Configuration. Lastly we exposed this
   lightweight interface as a configuration entry point for
   ExecutionEnvironments. This change will make it possible to pass the
   ReadableConfig directly to the StateBackendFactories without fragile
   adapters.
   
   
   ## Brief change log
   
     - Replaced Configuration with ReadableConfig for StateBackends 
configuration
     - Changed type of `TIMER_SERVICE_FACTORY` option
     - Removed `ReadableConfigToConfigurationAdapter.java`
   
   
   ## Verifying this change
   
   This change is already covered by existing tests.
   
   ## 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, Kubernetes/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