zozo123 commented on issue #74196: URL: https://github.com/apache/airflow/issues/74196#issuecomment-5997570017
Thanks @kadubhumika — **B, with a hard line** (this matches the acceptance criteria on this issue). Keep caller-provided outlets, including `[]`. When `wait_for_termination=False`, Airflow may still emit the normal **task-success** outlet event; that event means the Databricks run was **submitted**, not that a Unity/Delta table refreshed. Document that, and warn at init if outlets are set with fire-and-forget. Do **not** have the provider emit or upgrade any verified Unity/table-refresh asset event in fire-and-forget. Verified outputs only after the remote run succeeds (sync + deferrable completion). Authors who need "table ready" scheduling should use `wait_for_termination=True` or a sensor (see #74225), not fire-and-forget outlets. Please start on `DatabricksSQLStatementsOperator`, then mirror to RunNow/SubmitRun. Happy to review the first cut. -- 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]
