IgorBobic commented on issue #73678: URL: https://github.com/apache/airflow/issues/73678#issuecomment-6415092222
@dheerajturaga I understand that you want to clear the way for future features, which is nice. However as @rloredo mentions we use them as an organization feature. With traditional data modeling practices it commonplace to have bidirectional relations between facts and dimensions. So, in some case it is not an option to just move the model or split it up. Additionally, it generates a big generational overhead for the users of our platform. In our organization there are 32 DAGs that have circular task groups, here is a snippet of examples: <img width="411" height="684" alt="Image" src="https://github.com/user-attachments/assets/8d142379-05d0-42c4-98e3-b24bac1f5e80"; /> As I understand the plan is now to: 1. in 3.3.4 fix the UI and allow circular task groups 2. in 3.3.5 to make circular task groups breaking Is my understanding correct? If so, I would say it is essential for us to have some grouping functionality of our tasks, that can exist regardless of whether there are circular dependencies between those groups. I see there is this feature from astronomer cosmos called [group_nodes_by_folder](https://astronomer.github.io/astronomer-cosmos/guides/translate_dbt_to_airflow/render-config.html), which is currently broken as well. I also see that the [PR](https://github.com/astronomer/astronomer-cosmos/pull/3091) linked above should fix this. Can we assume that this feature will work even with circular dependencies existing between those folders in 3.3.5+? If not, will there be some support included in that patch that will allow some sort of grouping? Thanks in advance -- 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]
