-
Notifications
You must be signed in to change notification settings - Fork 59
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
[ADAP-1087] [Regression] Loosen redshift-connector pin #700
Comments
I have the same problem |
We can loosen this up somewhat, unfortunately |
This was resolved by #704 in version |
Now we can use a different dbt-connector but Airflow constrain file is tied to redshift-connector==2.014 so the problem is the same:
The conflict is caused by: |
@EsauOlivaLeaoHelix I don't think there is much this project can do about that. It looks like airflow 2.8 pins to redshift-connector 2.0.918 so that should work, but if you need airflow 2.7 I think you will have to provide your own constraints file for this (at your own risk of course) |
Is this a regression in a recent version of dbt-redshift?
Current Behavior
The redshift-connector dependency is hard pinned to a particular version. The comments in setup.py indicate that this is because redshift-connector does not follow SemVer and can release breaking changes at any time. However, this has the consequence of making this library much more difficult to install, particularly with the shift in python packaging to enforce constraints
A concrete example of this is Airflow 2.7, which uses the following default constraints:
https://raw.githubusercontent.com/apache/airflow/constraints-2.7.2/constraints-3.11.txt
You'll note the version of redshift-connector is
2.0.914
but this package jumped from2.0.913
directly to2.0.915
, so it is essentially uninstallable by default in AirflowExpected/Previous Behavior
pip install with constraint should still have a valid installation candidate
Steps To Reproduce
pip install dbt-redshift --constraint https://raw.githubusercontent.com/apache/airflow/constraints-2.7.2/constraints-3.11.txt
Relevant log output
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: