Refactor Asset Decorator to Use SdkDAG for Improved Modularity (#46927) #46936
+31
−63
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.
This PR introduces SdkDAG inside the SDK to replace the direct dependency on airflow.models.dag within the asset decorator. This improves modularity and aligns with the project’s architectural principles.
Changes:
Implemented SdkDAG within airflow.sdk.dag.
Updated asset decorators (@asset and @asset.multi) to use SdkDAG instead of airflow.models.dag.
Ensured compatibility with existing asset definitions.
Why This Change?
Addresses Issue #46927.
Provides a structured way to define DAGs within the SDK.
Improves maintainability by reducing dependencies on core Airflow modules.
Next Steps:
Run full test suite to validate the changes.
Gather feedback from maintainers for further refinements.