dabla commented on PR #74201: URL: https://github.com/apache/airflow/pull/74201#issuecomment-6836828593
Fair question. For a single task you're right: one run is no faster, and the table only applies once several runs share a loop. The use case is agent runs inside an iterated async task (#62922): N runs share one loop in one process, which is what the numbers measure. That needs `aexecute` on the operator behind `@task.agent`, so this PR is the piece that lets the two work together once #62922 is in. The backport mentioned in the description ran eight runs that way in one task. A smaller one next to it: prompt functions with async-only inputs, such as an async hook or `Variable.aget` helpers shared with the other async tasks of the Dag. We run a daily report task like that. And `async def` under `@task.agent` currently fails in `validate_prompt` on the coroutine while the operator reports `is_async`, so it needs either this or an explicit error. `durable` and HITL are refused for now because they block during the run, not by design; they can follow once they have async paths. -- 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]
