You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/06/27 11:21:00 UTC

[GitHub] [flink] zhuzhurk opened a new pull request #8912: [FLINK-12709] [runtime] Implement new generation restart strategy loader which also respects legacy…

zhuzhurk opened a new pull request #8912: [FLINK-12709] [runtime] Implement new generation restart strategy loader which also respects legacy…
URL: https://github.com/apache/flink/pull/8912
 
 
   … restart strategy configs
   
   ## What is the purpose of the change
   
   *A loader is need to load factories of RestartBackoffTimeStrategy. In order to be backwards compatible, the loader should respect legacy RestartStrategy configurations. The legacy configuration can be in cluster config format (https://ci.apache.org/projects/flink/flink-docs-stable/dev/restart_strategies.html) or in RestartStrategies.RestartStrategyConfiguration format.*
   
   
   ## Brief change log
   
     - *The loader coverts legacy configuration into new generation format*
     - *The loader creates RestartBackoffTimeStrategy factory from new format configs*
   
   ## Verifying this change
   
     - *Added unit tests RestartBackoffTimeStrategyFactoryLoader*
   
   ## 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: (yes)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (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