zhuzhurk opened a new pull request #9365: [FLINK-13336] [docs] Remove the 
legacy batch fault tolerance page and redirect it to task failure recovery page
URL: https://github.com/apache/flink/pull/9365
 
 
   ## What is the purpose of the change
   
   The batch fault tolerance 
page(https://ci.apache.org/projects/flink/flink-docs-release-1.8/dev/batch/fault_tolerance.html)
 is describing a deprecated way to configure restart strategies.
   
   We should remove it and redirect it to the task failure recovery page 
(https://ci.apache.org/projects/flink/flink-docs-release-1.8/dev/restart_strategies.html)
 for latest description of the fault tolerance configurations, including 
restart strategies and failover strategies.
   
   ## Brief change log
   
     - *remove the legacy batch fault tolerance page*
     - *redirect the former links to task failure recovery page*
   
   
   ## Verifying this change
   
   This change is a docs cleanup without any test coverage.
   
   ## 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