Add backward compatibility with old versions of Apache Beam #27263
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.
The PR #23961 added support for impersonation of service accounts, but at the same time limited the supported versions of Apache Beam to 2.39.0. This is a very big limitation considering that this functionality is not critical and many existing pipelines require an older version. On the other hand, this restriction is not checked if the user installs beam in a separate virtual environment. On the other hand, this restriction is not checked if the user installs beam in a separate virtual environment. Then Apache Beam starts, but unsupported options are passed.
To solve these two problems, I moved the Apache Beam version check to runtime and use the old version restrictions in
providers.yaml
.Additionally, I will unblock the work on Snowpark integration which requires
cloudpickle
2.0.0 while Apache Beam 2.39.0 requirescloudpickle
2.1.0.CC: @lwyszomi
^ 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.