[
https://issues.apache.org/jira/browse/FLINK-17966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Knauf updated FLINK-17966:
-------------------------------------
Labels: (was: auto-closed)
Priority: Not a Priority (was: Minor)
> Documentation improvement of checkpointing API
> ----------------------------------------------
>
> Key: FLINK-17966
> URL: https://issues.apache.org/jira/browse/FLINK-17966
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.10.1
> Reporter: Vijaya Bhaskar V
> Priority: Not a Priority
>
> As per mail thread discussion:
> [https://lists.apache.org/thread.html/rfe38f6f15f35c28b3ea7865cee2a4dd1d31d93c8d212ad0723b9fd7b%40%3Cuser.flink.apache.org%3E]
> While using Flink REST Monitoring API's related to checkpoints:
> [https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html]
> , its better to give reference of
> [https://ci.apache.org/projects/flink/flink-docs-release-1.10/monitoring/checkpoint_monitoring.html#overview-tab]
> and retained check points:
> [https://ci.apache.org/projects/flink/flink-docs-stable/ops/state/checkpoints.html]
> and give example of various fields of it, in the scenarios
> a) When job has enough number of attempts after failure and recovery
> b) When job has retained check points, how the response looks like
> c) When the job has last but one attempt left and has already few check
> points left
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
