dshemetov commented on issue #70880: URL: https://github.com/apache/airflow/issues/70880#issuecomment-5153704608
> Is the behavior that you mentioned expected? It certainly seems like FIFO behavior is expected for non Asset-triggered dagruns (there are explicit unit tests checking that), so I'm extrapolating that we'd want Asset-triggered dagruns to be consistent with that. > Tasks in a DAG are still executing in the proper order, but you're saying that Tasks across multiple DAG runs are not? Sort of. The analog isn't exact, but if we were to, say, let those emitted Assets all pile up in a single consumer run, .expand() over those on the same `max_active_tis_per_dag=1` task, then the scheduler would use `task_instance.map_index` to order them consistently (assuming the Assets arrive to the consumer in emission order, I don't know if that's guaranteed). -- 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]
