Remove Airflow 3 Deprecation Warning dependency in OTel Provider #46600
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
hussein-awala
approved these changes
Feb 9, 2025
ashb
approved these changes
Feb 9, 2025
jscheffl
force-pushed
the
feature/remove-airflow3-deprecation-dependency-in-otel-provider
branch
from
470b64e to
13b6780
Compare
jscheffl
added
the
full tests needed
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
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.
As we are getting closer to Airflow 3, Deprecations warnings should not be warning for Airflow 3 anymore.
To be able to clean this also the AirflowContextDeprecationWarning needs to be removed in core, which OTel provider still depends on. Adding a small import indirection such that we can clean the core w/o breaking provider.