Update Databricks operators to match latest version of API 2.0 #19443
Conversation
alexott
force-pushed
the
databricks-add-new-parameters
branch
from
49720f1 to
d175040
Compare
|
Looked like intermittent problem. Closed/reopened to rebuild |
|
The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
github-actions
bot
added
the
okay to merge
|
Docs are failing @alexott |
|
Thank you @potiuk - I'll fix it. I run pre-commit, but it was failing on pulling the base docker image, or something like, so it looks like i missed the docs part |
This includes: - added support for `jar_params` in the `DatabricksRunNowOperator` - added support for `pipeline_task` in the `DatabricksSubmitRunOperator` Also, added documentation for `DatabricksRunNowOperator` this fixes apache#10786
alexott
force-pushed
the
databricks-add-new-parameters
branch
from
d175040 to
e6bebdf
Compare
|
Ok, docs are fixed. |
|
Awesome work, congrats on your first merged pull request! |
|
Thank you for help Jarek! Next PRs should be simpler, after I got familiar with the workflow & tooling |
|
Cool! Looking forward to it! |
2 participants
This includes:
jar_paramsin theDatabricksRunNowOperatorpipeline_taskin theDatabricksSubmitRunOperatorAlso, added documentation for
DatabricksRunNowOperatorcloses: #10786