Zakelly commented on code in PR #23679:
URL: https://github.com/apache/flink/pull/23679#discussion_r1387803896
##########
docs/content.zh/docs/deployment/cli.md:
##########
@@ -153,6 +153,35 @@ $ ./bin/flink savepoint \
Triggering the savepoint disposal through the `savepoint` action does not only
remove the data from
the storage but makes Flink clean up the savepoint-related metadata as well.
+### Creating a Checkpoint
+[Checkpoints]({{< ref "docs/ops/state/checkpoints" >}}) can also be manually
created to save the
+current state. To get the difference between checkpoint and savepoint, please
refer to
+[Checkpoints vs. Savepoints]({{< ref
"docs/ops/state/checkpoints_vs_savepoints" >}}). All that's
+needed to trigger a checkpoint manually is the JobID:
+```bash
+$ ./bin/flink checkpoint \
+ $JOB_ID
+```
+```
+Triggering checkpoint for job 99c59fead08c613763944f533bf90c0f.
+Waiting for response...
+Checkpoint(CONFIGURED) 26 for job 99c59fead08c613763944f533bf90c0f completed.
+You can resume your program from this checkpoint with the run command.
+```
+If you want to trigger a full checkpoint while the job periodically triggering
incremental checkpoints,
+please use the `--full` option.
Review Comment:
User selects `--incremental` flag in this case will trigger a full
checkpoint. This behavior align with the REST API. I think a possible way is to
remove the `--incremental` flag (or just remove it from the help messages and
documents). After we really support triggering a incremental checkpoint with
configured full checkpointing state backend, we add this flag back.
--
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
