Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raise deprecation warning when accessing inlet or outlet events through str #43922

Conversation

Lee-W
Copy link
Member

@Lee-W Lee-W commented Nov 12, 2024

This behavior will be removed in airflow 3 as assets have attributes name and uri, it would be confusing to identify which attribute should be used to filter the right asset


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

…et events through str

this behavior will be removed in airflow 3 as assets have attributes name and uri,
it would be confusing to identify which attribute should be used to filter the right asset
@Lee-W Lee-W force-pushed the add-deprecation-warning-for-using-string-to-access-outlet branch from f9bf3c2 to fb8a78c Compare November 12, 2024 11:07
@Lee-W Lee-W merged commit d29bc2c into apache:v2-10-test Nov 14, 2024
48 checks passed
@Lee-W Lee-W deleted the add-deprecation-warning-for-using-string-to-access-outlet branch November 14, 2024 00:36
@utkarsharma2 utkarsharma2 added the type:doc-only Changelog: Doc Only label Dec 4, 2024
@utkarsharma2 utkarsharma2 added this to the Airflow 2.10.4 milestone Dec 4, 2024
utkarsharma2 pushed a commit that referenced this pull request Dec 4, 2024
…et events through str (#43922)

this behavior will be removed in airflow 3 as assets have attributes name and uri,
it would be confusing to identify which attribute should be used to filter the right asset
utkarsharma2 pushed a commit that referenced this pull request Dec 9, 2024
…et events through str (#43922)

this behavior will be removed in airflow 3 as assets have attributes name and uri,
it would be confusing to identify which attribute should be used to filter the right asset
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants