[
https://issues.apache.org/jira/browse/FLINK-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16050:
-----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: stale-major
>
> 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.3.4#803005)
