ashb commented on issue #16764: URL: https://github.com/apache/airflow/issues/16764#issuecomment-875549047
Oh yeah. Okay, so why this happens: TaskGroups don't actually exist as dependencies, so when you do `start >> taskgroup >> end` you are setting the downstream of start and the upstream of end based on the _current_ tasks in the taskgroup. To fix this properly we would need need a "two pass" approach (which I think, isn't a problem): the first pass happens when parsing the DAG file, and when we do `start >> taskgroup` we store the Actual TaskGroup there, and only in the second pass (likely when we "bag" the DAG, handled internally in the parsing process of Airflow) is when we'd turn TaskGroups in the dependencies in to their actual values. -- 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]
