1fanwang commented on issue #70953: URL: https://github.com/apache/airflow/issues/70953#issuecomment-5186694293
Verified [Validate DatabricksSQLStatementsSensor statement fields after rendering](https://github.com/apache/airflow/pull/70340) on `databricks 7.18.1rc1`. Works as intended. Airflow 3.3.0, two identical virtualenvs: one with the RC providers, one with the previous stable release. Same Dag, same command, run through the real task runner. RPC is stubbed, and the stub asserts the value that actually reaches it. A `DatabricksSQLStatementsSensor` with `statement="SELECT 1"` and a templated `statement_id` that renders to empty, so only one of the two is set after rendering. ```bash # databricks 7.18.1rc1 AIRFLOW_HOME=$PWD/airflow_home \ AIRFLOW__CORE__DAGS_FOLDER=$PWD/dags_e2e/rc_70340_databricks_sql_sensor \ .venv/bin/airflow dags test rc_70340_databricks_sql_sensor # databricks 7.18.0, identical Dag AIRFLOW_HOME=$PWD/airflow_home_prev \ AIRFLOW__CORE__DAGS_FOLDER=$PWD/dags_e2e/rc_70340_databricks_sql_sensor \ .venv-prev/bin/airflow dags test rc_70340_databricks_sql_sensor ``` ``` # databricks 7.18.1rc1 RC_CHECK_OK statement submitted: 'SELECT 1' state=success # databricks 7.18.0, no task ever runs Error loading DAG from rc_70340_databricks_sql_sensor.py: AirflowException: Cannot provide both statement and statement_id. ``` -- 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]
