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 ac03ede6f75 Warn about the DatabricksSQLStatementsSensor exclusivity
tightening (#72761)
ac03ede6f75 is described below
commit ac03ede6f759e47c9b5daad2aae4c90f3837f187
Author: Noritaka Sekiyama <[email protected]>
AuthorDate: Thu Sep 10 05:48:05 2026 +0900
Warn about the DatabricksSQLStatementsSensor exclusivity tightening (#72761)
The sensor's exclusivity check moved to Dag parse time and now treats an
empty
string as a provided value, so a pairing that ran the statement in the
released
7.19.0 fails at parse time instead. The note was asked for while #70831 was
in
review and the PR merged before it landed, leaving users upgrading past
7.19.0
with no explanation of the failure.
---
providers/databricks/docs/changelog.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/providers/databricks/docs/changelog.rst
b/providers/databricks/docs/changelog.rst
index 5f6fbc15ee1..f928f711930 100644
--- a/providers/databricks/docs/changelog.rst
+++ b/providers/databricks/docs/changelog.rst
@@ -26,6 +26,16 @@
Changelog
---------
+.. warning::
+ ``DatabricksSQLStatementsSensor`` now rejects the combination of
``statement`` and
+ ``statement_id`` when the Dag is parsed rather than when the task runs, and
the check is
+ ``is not None``, so an empty string counts as provided. ``statement="SELECT
1"`` together
+ with ``statement_id=""`` — or with a ``statement_id`` template that renders
to ``None``
+ under ``render_template_as_native_obj=True`` — ran the statement in 7.19.0
and now raises
+ at Dag parse time. Pass exactly one of the two and omit the other entirely
instead of
+ passing an empty value. The argument-validation errors in this sensor are
also now
+ ``ValueError`` rather than ``AirflowException``.
+
7.19.0
......
