dawidwys opened a new pull request #18086:
URL: https://github.com/apache/flink/pull/18086


   ## What is the purpose of the change
   
   We introduce NO_CLAIM restore mode in which we do not take ownership of
   the restored checkpoint. We do enforce the first, successful checkpoint
   after a restore to be "full" meaning it can not share any artefacts with
   the initial one.
   
   Taking a "full" snapshot needs support from state backend, therefore we
   add a method supportsFullSnapshots to the Snapshottable interface, so
   that state backend can add support incrementally. If a state backend
   does not support forces snapshots, user can switch to either the LEGACY
   mode or CLAIM mode.
   
   
   ## Verifying this change
   
   Added:
   * IT test: `SavepointITCase.testTriggerSavepointAndResumeWithNoClaim`
   * `StreamTaskTest.testForceFullSnapshotOnIncompatibleStateBackend`
   
   
   ## 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, 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): will be documented in a separate effort
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to