mirror of
https://github.com/apache/airflow.git
synced 2026-11-04 15:53:05 +00:00
* Java SDK: Resolve a task's arguments from the Dag's own wiring A Dag authored in Java has no Python call site, so the supervisor sends no argument bindings for it and a task's data parameters had nothing to resolve against. Where the Dag wired inputs for a task, those stand in; a stub-backed task keeps reading its bindings, including when the call site bound none. The authoring surface that records those inputs lands in the next commit, so nothing declares them yet. * Keep taskDef out of Context's constructor and reuse resolveWiredAll * Use ADR-0007 wording for the wired-arity warning