[
https://issues.apache.org/jira/browse/FLINK-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283595#comment-17283595
]
Matthias Pohl edited comment on FLINK-16050 at 8/17/23 9:34 AM:
----------------------------------------------------------------
[~vthinkxie] [~lining] What's the progress on this issue? It's mentioned in
FLIP-100 -which is labeled as {{released}} in {{1.11}}-. In contrast, the Jira
issue itself is still open/in progress?
was (Author: mapohl):
[~vthinkxie] [~lining] What's the progress on this issue? It's mentioned in
FLIP-100 which is labeled as {{released}} in {{1.11}}. In contrast, the Jira
issue itself is still open/in progress?
> Add Attempt Information
> -----------------------
>
> Key: FLINK-16050
> URL: https://issues.apache.org/jira/browse/FLINK-16050
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST, Runtime / Web Frontend
> Reporter: lining
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> According to the
> [docs|https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jobs-jobid-vertices-vertexid-subtasks-subtaskindex],
> there may exist more than one attempt in a subtask, but there is no way to
> get the attempt history list in the REST API, users have no way to know if
> the subtask has failed before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
