[FLINK-40254][docs] Document checkpoint behavior after a CLAIM-mode restore from a NATIVE savepoint - #28838
Open
Savonitar wants to merge 1 commit into
Open
[FLINK-40254][docs] Document checkpoint behavior after a CLAIM-mode restore from a NATIVE savepoint#28838Savonitar wants to merge 1 commit into
Savonitar wants to merge 1 commit into
Conversation
Merged
1 task
snuyanzin
requested changes
Jul 30, 2026
snuyanzin
left a comment
snuyanzin
left a comment
Contributor
There was a problem hiding this comment.
Thanks for contribution
since you use AI, can you use Generated-by: instead of Co-authored-by: as mentioned in Apache recommendations https://www.apache.org/legal/generative-tooling.html
also the doc about this is in https://github.com/apache/flink/pull/27776/changes#r2979585031
…estore from a NATIVE savepoint Since FLINK-39964, the first incremental checkpoint(s) taken after a CLAIM-mode restore from a NATIVE savepoint reference the reused savepoint files by their absolute location. Extend the CLAIM-mode note on the savepoints page (EN and ZH): such checkpoints are neither self-contained nor relocatable (consistent with incremental checkpoints in general), and the savepoint directory remains referenced, with its files' lifecycle managed by Flink, until every checkpoint reusing its files has been subsumed. Generated-by: Claude Fable 5
Savonitar
force-pushed
the
FLINK-40254-docs
branch
from
July 30, 2026 08:53
e8db982 to
2d417fe
Compare
Contributor
Author
|
@snuyanzin thanks for sharing the links. Done! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since FLINK-39964, the first incremental checkpoint(s) taken after a CLAIM-mode restore from a NATIVE savepoint reference the reused savepoint files by their absolute location. Extend the CLAIM-mode note on the savepoints page (EN and ZH): such checkpoints are neither self-contained nor relocatable (consistent with incremental checkpoints in general), and the savepoint directory remains referenced, with its files' lifecycle managed by Flink, until every checkpoint reusing its files has been subsumed.
What is the purpose of the change
This pull request updates documents for checkpoint behavior after a CLAIM-mode restore from a NATIVE savepoint.
Brief change log
Update EN and ZH docs.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Fable 5