killzoner opened a new pull request, #1949: URL: https://github.com/apache/datafusion-ballista/pull/1949
# Which issue does this PR close? Closes https://github.com/apache/datafusion-ballista/issues/1795, follow up to https://github.com/apache/datafusion-ballista/pull/1903 # Rationale for this change Expose tasks for failed stages in REST API, handle it in TUI # What changes are included in this PR? - Switch StageTaskResponse->status to use new `StageTaskStatus` - Expose stage error with both `reason` and original `error` (common wrapping for underlying errors) - Display short label (only `reason`) in failed task for TUI Tested locally with TPC-H under the chaos fault generator: ```bash cargo run --bin ballista-scheduler --features prometheus-metrics cargo run --bin ballista-executor cargo run --bin tpch -- benchmark ballista -p /path/to/tpch/sf10 -f parquet -i 1 \ --port 50050 --host 127.0.0.1 \ -c datafusion.execution.target_partitions=24 \ -c ballista.planner.adaptive.enabled=true \ -c ballista.testing.chaos_execution.enabled=true \ -c ballista.testing.chaos_execution.fault_type=fatal \ -c ballista.testing.chaos_execution.probability=0.6 \ -q 1 ``` Failed job in the TUI: **Global view** (job shows `Failed`): <img width="1897" height="151" alt="Screenshot from 2026-07-05 14-28-05" src="https://github.com/user-attachments/assets/982bb369-9f46-4dad-90b1-748f8df3341d"; /> **Stage detail**: <img width="1619" height="116" alt="Screenshot from 2026-07-05 14-28-59" src="https://github.com/user-attachments/assets/7fd63fc0-4aff-4a02-9c9b-562e90e04f86"; /> **Stage tasks** (was empty for a failed stage, now proper list): <img width="1878" height="460" alt="Screenshot from 2026-07-05 14-28-29" src="https://github.com/user-attachments/assets/f374e623-8141-445f-9bbd-888417a14b1a"; /> # Are there any user-facing changes? `Failed` task will now display `ExecutionError` or other reason, but they were not displayed anyway before this fix, so no real user facing change. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
