ljz2051 opened a new pull request, #24402:
URL: https://github.com/apache/flink/pull/24402

   ## What is the purpose of the change
   
   This pull request split 'state.backend.local-recovery' into two options: 
"execution.checkpointing.local-backup.enabled" and 
"execution.state-recovery.from-local".  The 
"execution.checkpointing.local-backup.enabled" indicates whether to do 
checkpoint on local disk; while "execution.state-recovery.from-local" option 
specifies whether to recover from local.
   
   ## Brief change log
   - Move LOCAL_RECOVERY config from CheckpointingOptions to 
StateRecoveryOptions
   - Split 'state.backend.local-recovery' into two options for checkpointing 
and recovery
   - Add UT/IT tests to verify localBackup and localRecovery configs
   
   ## Verifying this change
   
   The added tests and existing tests can cover this change, which can be 
verified as follows:
   - 
TaskExecutorLocalStateStoresManagerTest#testStateStoreDirectoryCreateAndDeleteWithLocalRecoveryEnabled
 and testStateStoreDirectoryCreateAndDeleteWithLocalBackupEnabled   (added 
tests)
   - TaskLocalStateStoreImplTest#TaskLocalStateStoreImplTest  (added tests)
   - LocalRecoveryITCase & TaskExecutorLocalStateStoresManagerTest &  
TaskLocalStateStoreImplTest (existing tests )
   
   ## 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)`: yes
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, 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? docs
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to