Add backward compatibility for old Airflow versions for CloudComposerDAGRunSensor#46011
Merged
potiuk merged 1 commit intoapache:mainfrom Jan 26, 2025
Merged
Conversation
eladkal
reviewed
Jan 24, 2025
providers/src/airflow/providers/google/cloud/sensors/cloud_composer.py
Outdated
Show resolved
Hide resolved
dbf0024 to
f73a882
Compare
potiuk
approved these changes
Jan 26, 2025
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
niklasr22
pushed a commit
to niklasr22/airflow
that referenced
this pull request
Feb 8, 2025
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
In this PR I have added backward compatibility for old Airflow versions for CloudComposerDAGRunSensor.
By this PR #43902 inside the Airflow core for the DAG model
execution_datewas changed to thelogical_date. This change was made for Airflow 3, but because it was renamed for the whole codebase it affected Google provider. The problem was faced , because the new google provider was released before Airflow 3.^ 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.rstor{issue_number}.significant.rst, in newsfragments.