zozo123 commented on issue #74196: URL: https://github.com/apache/airflow/issues/74196#issuecomment-5997617090
Thanks @kadubhumika — and sorry for the wait. Really appreciate you asking this before coding. Please go with **B**, gently: keep caller-provided outlets as set (including `[]`), and let Airflow’s normal task-success outlet behavior stand when `wait_for_termination=False`. In that mode the event means the Databricks run was **submitted**, not that a Unity/Delta table refreshed — so please document that clearly, and add a friendly init warning if outlets are set with fire-and-forget. Please don’t have the provider emit or upgrade any verified Unity/table-refresh asset event in fire-and-forget. Verified outputs only after the remote run actually succeeds (sync and deferrable completion). Authors who need “table ready” scheduling are better served by `wait_for_termination=True` or a sensor (see #74225). Starting with `DatabricksSQLStatementsOperator` is perfect; we can mirror to RunNow/SubmitRun once that looks good. Happy to review the first cut — shout if anything is unclear. -- 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]
