Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.1.0
-
None
Description
angerszhuuu and ron8hu discussed a generic and consistent way for overall stages, i.e. endpoint /application/{app-id}/stages. It can be:
/application/{app-id}/stages?details=[true|false]&status=[ACTIVE|COMPLETE|FAILED|PENDING|SKIPPED]&withSummaries=[true|false]&taskStatus=[RUNNING|SUCCESS|FAILED|KILLED|PENDING]
where
- query parameter details=true is to show the detailed task information within each stage. The default value is details=false;
- query parameter status can select those stages with the specified status. When status parameter is not specified, a list of all stages are generated.
- query parameter withSummaries=true is to show both task metrics summary information in percentile distribution (see example of a single stage in taskMetricsDistributions.json
) and executor metrics summary information in percentile distribution (see example of a single stage in executorMetricsDistributions.json ). The default value is withSummaries=false. - query parameter taskStatus is to show only those tasks with the specified status within their corresponding stages. This parameter can be set when details=true (i.e. this parameter will be ignored when details=false).
The output is an aggregate of all stages meeting the filtering conditions for a given application.
