sduvvuri26 opened a new pull request, #68622: URL: https://github.com/apache/airflow/pull/68622
## Summary Clarifies `databricks_retry_delay` / `retry_delay` documentation for Databricks operators, hooks, and triggers. The previous docs described a fixed number of seconds between retries. The default implementation uses **exponential backoff** with `retry_delay` as the **minimum** wait (`wait_exponential` in `BaseDatabricksHook`). Note: `databricks_retry_args` can override the default wait strategy; this documents the default behavior only. ## Test plan - [x] Doc-only change (docstrings + repos operator RST tables) - [x] Verified retry behavior manually with `DatabricksSubmitRunOperator` and a broken connection (`retry_delay=1` and `retry_delay=20`) ## Manual verification Observed retry timing with `DatabricksSubmitRunOperator`, broken connection, `databricks_retry_limit=10`: | `retry_delay` | Observed waits between attempts | |---------------|----------------------------------| | `1` | 1s, 2s, 4s, 8s, 16s, 32s, … | | `20` | 20s × 5, then 32s, 64s, 128s, … | This matches `wait_exponential(min=retry_delay, max=2**retry_limit)` in `BaseDatabricksHook`. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Cursor Generated-by: Cursor following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
