apache
Inconsistent Task Ordering between grid view and graph view.
Apache Airflow version
3.0.1
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Inconsistent Task Ordering in the* Grid View. *The task order in the Grid view appears to be different from what we see in the Graph view.
What you think should happen instead?
No response
How to reproduce
I tried replicating the issue by making complex task groups dependency but not able to replicate. But as we see in the comments, community members are also facing this issue.
Operating System
Linux
Versions of Apache Airflow Providers
No response
Deployment
Other
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
I think I have the same behavior (3.0.1) which I described on SO : https://stackoverflow.com/questions/79659430/problem-with-tasks-and-tasks-groups-order-on-the-grid-view-on-airflow-3-0-1
@vimchun is it possible for you to add the simpler dag code with which we can reproduce this issue? I tried reproducing with simpler dag code but could not.
@atul-astronomer I figured out I don't have this issue on 3.0.1 anymore with the appropriate bitshift operators for the tasks dependencies. I already had some of them, but I think some of them were missing.
I was a bit confused because :
- the 3.0.1 graph view understood without all the tasks dependencies.
- the 2.11.0 graph view and grid view understood without all the tasks dependencies.
Now I have the grid view matching the graph view :
@bbovenzi No, I don't reproduce this issue anymore after I defined all the tasks dependencies properly. I reproduced the issue on 3.0.1 (inconsistent tasks ordering between grid view and graph view), only when some of the tasks dependencies were missing (so I don't really consider this as an issue in my case, although it worked well on 2.11.0 when those last tasks dependencies were missing). I did not find other issues mentionning that, but I think @atul-astronomer opened this issue before I opened mine on SO, so maybe it happens to other users, with other scenarios...
@atul-astronomer are you still experiencing this on latest main? Similarly to @vimchun are task dependencies properly set in your dag?
We are not able to replicate this issue with simpler dag and for now its only reproducible with client's dag. @rawwar has replaced all the complex operators with the EmptyOperator in client's code, and still we are not able to replicate this. We have shared the updated dag code with client and waiting for the response.
Reopening this as I've trimmed most of the tasks in the Original dag. Its now, down to 232 tasks. I'll be sharing the minimal reproducible code in next few days
