-
Notifications
You must be signed in to change notification settings - Fork 40
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
Upgrade snowflake-sqlalchemy package #1185
Conversation
Codecov ReportBase: 94.17% // Head: 94.17% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #1185 +/- ##
=======================================
Coverage 94.17% 94.17%
=======================================
Files 13 13
Lines 498 498
Branches 50 50
=======================================
Hits 469 469
Misses 20 20
Partials 9 9 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
python-sdk/pyproject.toml
Outdated
@@ -59,7 +59,7 @@ google = [ | |||
] | |||
snowflake = [ | |||
"apache-airflow-providers-snowflake", | |||
"snowflake-sqlalchemy>=1.2.0,<=1.2.4", | |||
"snowflake-sqlalchemy>=1.4.3,<1.5.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it cause any problems if we increase the version from 1.2.0 to 1.4.3 and a customer has some other things which depend on 1.2.0 in the env?
python-sdk/pyproject.toml
Outdated
@@ -23,7 +23,7 @@ dependencies = [ | |||
"pyarrow", | |||
"python-frontmatter", | |||
"smart-open", | |||
"SQLAlchemy>=1.3.18" | |||
"SQLAlchemy>=1.3.18,<1.4.42" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why we are restricting maybe a comment would be helpful
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have it as part of the PR description, but no harm in adding in the code as well, will do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have a ticket to unpin this? Do we need the rfc
imports?
|
Thanks for the explanation. Could you add the 2nd statement to the PR description, please? And to the comment :) |
@feluelle Added it in the PR and comment |
# Description ## What is the current behavior? Due to [changes](snowflakedb/snowflake-sqlalchemy#350) in `sqlalchemy==1.4.42` our CI is failing, since snowflake-sqlalchemy's rfc imports are failing and we cannot change the version of snowflake-sqlalchemy to anything other than 1.2.4 because airflow 2.2.5 has a constraint. ## What is the new behavior? Upgraded the package to 1.4.3 where the fix is added. ## Does this introduce a breaking change? Nope
Description
What is the current behavior?
Due to changes in
sqlalchemy==1.4.42
our CI is failing, since snowflake-sqlalchemy's rfc imports are failing and we cannot change the version of snowflake-sqlalchemy to anything other than 1.2.4 because airflow 2.2.5 has a constraint.What is the new behavior?
Upgraded the package to 1.4.3 where the fix is added.
Does this introduce a breaking change?
Nope