[airflow] deprecated subdagoperator (AIR304) #14628
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Same as for #14616 Let's first propose a set of rules that you plan of adding. I want to avoid having 50 or so airflow rules in ruff. |
|
|
@abhishekbhakat can we convert this PR back to draft state or close it if it's no longer needed according to the new airflow deprecation rules. It would help me to get a better sense for which PRs need my attention. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Airflow 3.0 deprecates the SubDagOperator in favor of TaskGroups. SubDagOperator has been known to cause deadlocks and performance issues, and will be removed in Airflow 3.0. This rule detects usage of SubDagOperator to help users migrate their DAGs to the more reliable TaskGroup pattern.
Ref: #14626
Test Plan
A test fixture has been included for the rule demonstrating both the deprecated SubDagOperator usage and the recommended TaskGroup alternative.