This is an automated email from the ASF dual-hosted git repository.
eladkal pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 13a5ac09f97 Fix Databricks retry parameter names in deferrable-mode
docs (#76744)
13a5ac09f97 is described below
commit 13a5ac09f970b59e1851b0481a238143bb2da856
Author: Noritaka Sekiyama <[email protected]>
AuthorDate: Mon Nov 9 22:45:09 2026 +0900
Fix Databricks retry parameter names in deferrable-mode docs (#76744)
The deferrable-mode retry section told users to set retry_limit and
retry_delay on the operator. retry_delay is the BaseOperator task retry
interval, so following the docs changed task retries instead of the
Databricks API retry policy, and retry_limit is not an operator argument.
Related: #64609
Co-authored-by: Isaac <[email protected]>
---
providers/databricks/docs/operators/run_now.rst | 4 ++--
providers/databricks/docs/operators/submit_run.rst | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/providers/databricks/docs/operators/run_now.rst
b/providers/databricks/docs/operators/run_now.rst
index cbc2da28c82..64345c8f135 100644
--- a/providers/databricks/docs/operators/run_now.rst
+++ b/providers/databricks/docs/operators/run_now.rst
@@ -191,8 +191,8 @@ the common safe choices.
For controlling attempt count and delay in deferrable mode, leave
``databricks_retry_args`` unset and use the dedicated operator parameters
-``retry_limit`` and ``retry_delay``. When ``databricks_retry_args`` is set,
-these dedicated parameters are ignored for the hook retry policy.
+``databricks_retry_limit`` and ``databricks_retry_delay``. When
``databricks_retry_args`` is
+set, these dedicated parameters are ignored for the hook retry policy.
Serialization validation only verifies that values can cross the trigger
boundary; it does
not verify that the supplied keys and values are valid or meaningful
``tenacity.Retrying``
diff --git a/providers/databricks/docs/operators/submit_run.rst
b/providers/databricks/docs/operators/submit_run.rst
index 8124b928095..6964e96e79e 100644
--- a/providers/databricks/docs/operators/submit_run.rst
+++ b/providers/databricks/docs/operators/submit_run.rst
@@ -260,8 +260,8 @@ the common safe choices.
For controlling attempt count and delay in deferrable mode, leave
``databricks_retry_args`` unset and use the dedicated operator parameters
-``retry_limit`` and ``retry_delay``. When ``databricks_retry_args`` is set,
-these dedicated parameters are ignored for the hook retry policy.
+``databricks_retry_limit`` and ``databricks_retry_delay``. When
``databricks_retry_args`` is
+set, these dedicated parameters are ignored for the hook retry policy.
Serialization validation only verifies that values can cross the trigger
boundary; it does
not verify that the supplied keys and values are valid or meaningful
``tenacity.Retrying``
