This is an automated email from the ASF dual-hosted git repository.
hangxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new fb7324b05bb [FLINK-33679][checkpointing] Fix the misleading
description about RestoreMode#LEGACY(#24101)
fb7324b05bb is described below
commit fb7324b05bbc11a92a686e8d7c3cfe5ef39be148
Author: Zakelly <zakelly....@gmail.com>
AuthorDate: Tue Jan 16 18:36:40 2024 +0800
[FLINK-33679][checkpointing] Fix the misleading description about
RestoreMode#LEGACY(#24101)
---
docs/layouts/shortcodes/generated/savepoint_config_configuration.html | 2 +-
.../src/main/java/org/apache/flink/runtime/jobgraph/RestoreMode.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
a/docs/layouts/shortcodes/generated/savepoint_config_configuration.html
b/docs/layouts/shortcodes/generated/savepoint_config_configuration.html
index 2a40bd78b33..13baca7c989 100644
--- a/docs/layouts/shortcodes/generated/savepoint_config_configuration.html
+++ b/docs/layouts/shortcodes/generated/savepoint_config_configuration.html
@@ -12,7 +12,7 @@
<td><h5>execution.savepoint-restore-mode</h5></td>
<td style="word-wrap: break-word;">NO_CLAIM</td>
<td><p>Enum</p></td>
- <td>Describes the mode how Flink should restore from the given
savepoint or retained checkpoint.<br /><br />Possible values:<ul><li>"CLAIM":
Flink will take ownership of the given snapshot. It will clean the snapshot
once it is subsumed by newer ones.</li><li>"NO_CLAIM": Flink will not claim
ownership of the snapshot files. However it will make sure it does not depend
on any artefacts from the restored snapshot. In order to do that, Flink will
take the first checkpoint as a f [...]
+ <td>Describes the mode how Flink should restore from the given
savepoint or retained checkpoint.<br /><br />Possible values:<ul><li>"CLAIM":
Flink will take ownership of the given snapshot. It will clean the snapshot
once it is subsumed by newer ones.</li><li>"NO_CLAIM": Flink will not claim
ownership of the snapshot files. However it will make sure it does not depend
on any artefacts from the restored snapshot. In order to do that, Flink will
take the first checkpoint as a f [...]
</tr>
<tr>
<td><h5>execution.savepoint.ignore-unclaimed-state</h5></td>
diff --git
a/flink-runtime/src/main/java/org/apache/flink/runtime/jobgraph/RestoreMode.java
b/flink-runtime/src/main/java/org/apache/flink/runtime/jobgraph/RestoreMode.java
index da6c325265a..14bac3c083b 100644
---
a/flink-runtime/src/main/java/org/apache/flink/runtime/jobgraph/RestoreMode.java
+++
b/flink-runtime/src/main/java/org/apache/flink/runtime/jobgraph/RestoreMode.java
@@ -37,7 +37,7 @@ public enum RestoreMode implements DescribedEnum {
+ " Flink will take the first checkpoint as a full one,
which means it might"
+ " reupload/duplicate files that are part of the restored
checkpoint."),
LEGACY(
- "This is the mode in which Flink worked so far. It will not claim
ownership of the"
+ "This is the mode in which Flink worked until 1.15. It will not
claim ownership of the"
+ " snapshot and will not delete the files. However, it
can directly depend on"
+ " the existence of the files of the restored checkpoint.
It might not be safe"
+ " to delete checkpoints that were restored in legacy
mode ");
