Description
I've noticed that in Airflow 3, the tasks in the grid view might not be sorted topologically.
There is a small complexity in resolving it due to the Dag versioning, i.e., according to which version the tasks should be ordered, as it could change between versions. For starters, we could assume the latest version - and later maybe customize it according to a specfic version, similar as we do in the graph view.
It should be easier to resolve after merging #52286 (#53216), when we have the version queries ready in the grid view.
Use case/motivation
Assuming the following graph view:
Its current grid view:
but it would make more sense that the order in the latter would be:
get_nums -> process_number [] -> log_num.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Description
I've noticed that in Airflow 3, the tasks in the grid view might not be sorted topologically.
There is a small complexity in resolving it due to the Dag versioning, i.e., according to which version the tasks should be ordered, as it could change between versions. For starters, we could assume the latest version - and later maybe customize it according to a specfic version, similar as we do in the graph view.
It should be easier to resolve after merging #52286 (#53216), when we have the version queries ready in the grid view.
Use case/motivation
Assuming the following graph view:
Its current grid view:
but it would make more sense that the order in the latter would be:
get_nums -> process_number [] -> log_num.Related issues
No response
Are you willing to submit a PR?
Code of Conduct