-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
DatabricksSubmitRunOperator Get failed for Multi Task Databricks Job Run #28812
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
This has been tested with apache-airflow-providers-databricks version 3.2.0 and 4.0.0 versions as well |
If possible, please share the source code of DAG as well |
Really stacktrace doesn't match to release 2.3.2: https://github.com/apache/airflow/blob/2.3.2/airflow/providers/databricks/operators/databricks.py#L90 |
Even in provider 3.2.0 where the #25286 is fixed by #25427, the line doesn't match: https://github.com/apache/airflow/blob/providers-databricks/3.2.0/airflow/providers/databricks/operators/databricks.py#L90 |
Its not working even in later version 2.3.2 |
notebook_run = DatabricksSubmitRunOperator(task_id=f"test_",databricks_conn_id='test', json=json,polling_period_seconds=60, do_xcom_push=False) |
2.3.2 didn't include the fix, but lines in the stacktrace doesn't match any of versions |
Issue is really fixed by #25427 - customer confirmed that upgrade to the latest version of provider fixed it. |
Apache Airflow Provider(s)
databricks
Versions of Apache Airflow Providers
As we are running DatabricksSubmitRunOperator to run multi task databricks job as I am using airflow providers with mostly all flavours of versions, but when the databricks job get failed, DatabricksSubmitRunOperator gives below error its because this operator running get-output API, hence taking job run id instead of taking task run id
Error
Apache Airflow version
2.3.2
Operating System
macos
Deployment
Other
Deployment details
No response
What happened
No response
What you think should happen instead
No response
How to reproduce
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: