[GitHub] [airflow] alex-astronomer commented on issue #16764: TaskGroup dependencies handled inconsistently

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

alex-astronomer commented on issue #16764:
URL: https://github.com/apache/airflow/issues/16764#issuecomment-1014913471


   I think in order to really tackle this one, there are two issues here that need to be addressed.
   
   1. Just like the ticket mentions, we do expect that the TaskGroup can be a part of the dependency chain right?  So if someone were to build a dependency like the "broken" example from this ticket, then the tasks would still all be connected like they are supposed to be.  That would be my understanding at least, from the perspective of a user rather than a developer.  By using the taskgroup as a "top-level" dependency, and handling all "sub-dependencies" within the TaskGroup separately, I think this problem could be solved.
   2. The graph view and tree view are showing inconsistencies, and my understanding is that the tree view dependencies are being honored in this case, rather than the ones that are showing in the graph view.
   
   I believe that by solving these two problems independently, with respect to the bugs that are involved with TaskGroups, as shown in this Issue, will give a better base for the platform and provide a better integration with TaskGroups.  Thoughts on anything that I've written here?  I also believe that one solution may also inform the other.  I know that you've already come up with some ideas @ashb but I'm really curious to see how you feel about tackling the two problems that I've given here separately, using one to inform the other.


-- 
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: commits-unsubscribe@airflow.apache.org

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