-
- Downloads
[SPARK-19069][CORE] Expose task 'status' and 'duration' in spark history server REST API.
## What changes were proposed in this pull request? Although Spark history server UI shows task ‘status’ and ‘duration’ fields, it does not expose these fields in the REST API response. For the Spark history server API users, it is not possible to determine task status and duration. Spark history server has access to task status and duration from event log, but it is not exposing these in API. This patch is proposed to expose task ‘status’ and ‘duration’ fields in Spark history server REST API. ## How was this patch tested? Modified existing test cases in org.apache.spark.deploy.history.HistoryServerSuite. Author: Parag Chaudhari <paragpc@amazon.com> Closes #16473 from paragpc/expose_task_status.
Showing
- core/src/main/scala/org/apache/spark/status/api/v1/AllStagesResource.scala 2 additions, 0 deletions...la/org/apache/spark/status/api/v1/AllStagesResource.scala
- core/src/main/scala/org/apache/spark/status/api/v1/api.scala 2 additions, 0 deletionscore/src/main/scala/org/apache/spark/status/api/v1/api.scala
- core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala 2 additions, 4 deletionscore/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala
- core/src/main/scala/org/apache/spark/ui/jobs/UIData.scala 8 additions, 0 deletionscore/src/main/scala/org/apache/spark/ui/jobs/UIData.scala
- core/src/test/resources/HistoryServerExpectations/one_stage_attempt_json_expectation.json 16 additions, 0 deletions...erverExpectations/one_stage_attempt_json_expectation.json
- core/src/test/resources/HistoryServerExpectations/one_stage_json_expectation.json 16 additions, 0 deletions...HistoryServerExpectations/one_stage_json_expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_expectation.json 40 additions, 0 deletions...istoryServerExpectations/stage_task_list_expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_from_multi_attempt_app_json_1__expectation.json 16 additions, 0 deletions...task_list_from_multi_attempt_app_json_1__expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_from_multi_attempt_app_json_2__expectation.json 16 additions, 0 deletions...task_list_from_multi_attempt_app_json_2__expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_w__offset___length_expectation.json 100 additions, 0 deletions...tions/stage_task_list_w__offset___length_expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_w__sortBy_expectation.json 40 additions, 0 deletions...erExpectations/stage_task_list_w__sortBy_expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_w__sortBy_short_names___runtime_expectation.json 40 additions, 0 deletions...ask_list_w__sortBy_short_names___runtime_expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_task_list_w__sortBy_short_names__runtime_expectation.json 40 additions, 0 deletions...task_list_w__sortBy_short_names__runtime_expectation.json
- core/src/test/resources/HistoryServerExpectations/stage_with_accumulable_json_expectation.json 16 additions, 0 deletions...Expectations/stage_with_accumulable_json_expectation.json
- project/MimaExcludes.scala 6 additions, 1 deletionproject/MimaExcludes.scala
Loading
Please register or sign in to comment