-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Limit Snowflake connector to< 2.7.2 #20395
Conversation
The Snowflake connector 2.7.2 requires pyarrow to be >=6.0.0 (but it has no "install_requires" for it - it checks it dynamically and prints warning when imported. We should limit the provider until apache-beam will remove the pyarrow < 6.0.0 limitation.
3cf51ed
to
bd5efd9
Compare
BTW. This should be temporary measure - there is an apache-beam 2.3.5rc5 as of December 16th and there pyarrow is < 7.0.0 |
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
The Snowflake connector 2.7.2 requires pyarrow to be >=6.0.0 (but it has no "install_requires" for it - it checks it dynamically and prints warning when imported. We should limit the provider until apache-beam will remove the pyarrow < 6.0.0 limitation. (cherry picked from commit 0050e44)
The Snowflake connector 2.7.2 requires pyarrow to be >=6.0.0 (but it has no "install_requires" for it - it checks it dynamically and prints warning when imported. We should limit the provider until apache-beam will remove the pyarrow < 6.0.0 limitation. (cherry picked from commit 0050e44)
The Snowflake connector 2.7.2 requires pyarrow to be >=6.0.0
(but it has no "install_requires" for it - it checks it
dynamically and prints warning when imported.
We should limit the provider until apache-beam will remove the
pyarrow < 6.0.0 limitation.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.