Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly handle output of the failed tasks #25427

Merged
merged 1 commit into from
Aug 3, 2022

Conversation

alexott
Copy link
Contributor

@alexott alexott commented Jul 31, 2022

In the Jobs API 2.1, we can't call get_run_output on the top-level Run ID because it's
not supported by API - we need to call this function on specific sub-run of the job, even
if it consists of the single task

closes: #25286
closes: #28812
related: #21709

In the Jobs API 2.1, we can't call `get_run_output` on the top-level Run ID because it's
not supported by API - we need to call this function on specific sub-run of the job, even
if it consists of the single task

closes: apache#25286
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DatabricksSubmitRunOperator Get failed for Multi Task Databricks Job Run Error description cannot be shown
2 participants