Taragolis commented on issue #35689:
URL: https://github.com/apache/airflow/issues/35689#issuecomment-1822388341
> have multiple task groups structured to run in parallel, each containing
a sequence of tasks that should be executed in a specific order.
> When using Concurrency: Airflow schedules the first task of each group (a,
d, g) to run simultaneously, followed by the second tasks of each group (b, e,
h), and so on. This approach does not maintain the sequential integrity of each
group.
I can't get what you want to active, but actually work as it expected and
designed due to parallel and distributive manier. If you need to run TaskGroup
tasks only after previous one completed then you need to run one after each
other, e.g.:
Task Group 1 >> Task Group 2 >> Task Group 3
---
I want to add information, that this feature (as well as many from
`area:TaskGroup`) unlikely would be implemented with current of implementation
and design of TaskGroup, right now it is just an namespace / nice UI feature.
There is no information about task group after it created, because it is
just a nice namespace with additional abilities during DAG creation, all other
information not available during DagRun because it transform into a prefix(es)
for task_id:
- No any API
- No DB Record for task group, except information in serialized_dag
--
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]
