Replace ydb limitation with yandexcloud exclusion #47142
Merged
Conversation
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
The apache#47105 wrongly assumed that the new ydb version caused the problem with grpc.io, it turned out however that the root cause was wrong grpcio specification for yandexcloud - where grpcio requirement did not match runtime check for version. Excluding the versions of yandexcloud (and asking them to yank those versions) should help in solving the problem and it should not limit users to upgrade to newer versions of yandexcloud (when they are not using apache.beam or other libraries that limit grpcio to < 1.68.1)
eladkal
approved these changes
Feb 27, 2025
vgvoleg
approved these changes
Feb 27, 2025
Member
Author
|
Also opened yandex-cloud/python-sdk#138 |
sunank200
approved these changes
Feb 27, 2025
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 28, 2025
The apache#47105 wrongly assumed that the new ydb version caused the problem with grpc.io, it turned out however that the root cause was wrong grpcio specification for yandexcloud - where grpcio requirement did not match runtime check for version. Excluding the versions of yandexcloud (and asking them to yank those versions) should help in solving the problem and it should not limit users to upgrade to newer versions of yandexcloud (when they are not using apache.beam or other libraries that limit grpcio to < 1.68.1)
Sharashchandra
pushed a commit
to Sharashchandra/airflow
that referenced
this pull request
Feb 28, 2025
The apache#47105 wrongly assumed that the new ydb version caused the problem with grpc.io, it turned out however that the root cause was wrong grpcio specification for yandexcloud - where grpcio requirement did not match runtime check for version. Excluding the versions of yandexcloud (and asking them to yank those versions) should help in solving the problem and it should not limit users to upgrade to newer versions of yandexcloud (when they are not using apache.beam or other libraries that limit grpcio to < 1.68.1)
Member
Author
|
And the buggy yandexcloud versions are yanked now. We can remove the exclusion |
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Apr 4, 2025
The apache#47105 wrongly assumed that the new ydb version caused the problem with grpc.io, it turned out however that the root cause was wrong grpcio specification for yandexcloud - where grpcio requirement did not match runtime check for version. Excluding the versions of yandexcloud (and asking them to yank those versions) should help in solving the problem and it should not limit users to upgrade to newer versions of yandexcloud (when they are not using apache.beam or other libraries that limit grpcio to < 1.68.1)
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.
The #47105 wrongly assumed that the new ydb version caused the problem with grpc.io, it turned out however that the root cause was wrong grpcio specification for yandexcloud - where grpcio requirement did not match runtime check for version.
Excluding the versions of yandexcloud (and asking them to yank those versions) should help in solving the problem and it should not limit users to upgrade to newer versions of yandexcloud (when they are not using apache.beam or other libraries that limit grpcio to < 1.68.1)
^ 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.