[GitHub] [airflow] tothandor commented on issue #16112: List only a single level of TaskGroup in tree view

[GitBox <gi...@apache.org>]

tothandor commented on issue #16112:
URL: https://github.com/apache/airflow/issues/16112#issuecomment-849720314


   Sure. 
   
   Here's a graph view collapsed and grouped with TaskGroup:
   ![image](https://user-images.githubusercontent.com/4449214/119849789-36cfcc00-bf0d-11eb-976b-dbcb22dcb496.png)
   
   And here it is expanded:
   ![image](https://user-images.githubusercontent.com/4449214/119849911-55ce5e00-bf0d-11eb-88ea-09ee4b2a2fa8.png)
   
   And the tree view (query names masked out):
   ![image](https://user-images.githubusercontent.com/4449214/119850291-b362aa80-bf0d-11eb-8495-5791def11d12.png)
   You may say it's not incomprehensible, but usually there are more task groups along the pipeline, where each contains 10 to 100 subtasks generated dynamically. Each leaf node gets repeated.
   
   Compare this to a classic grouping with SubDAGs.
   ![image](https://user-images.githubusercontent.com/4449214/119850770-20764000-bf0e-11eb-86eb-8593bca4dcff.png)
   
   And zooming to the `sql` subdag:
   ![image](https://user-images.githubusercontent.com/4449214/119850931-4865a380-bf0e-11eb-9fa4-3540b95ab4dd.png)
   
   Nice and flat. 
   
   I am aware of TaskGroup nesting, that's what I have mentioned "path" in parentheses, but that does not help.


-- 
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org