cbuffett opened a new issue, #31968:
URL: https://github.com/apache/airflow/issues/31968

   ### Apache Airflow version
   
   2.6.1
   
   ### What happened
   
   The 2.6.1-python3.7 constraints specify `pyarrow==9.0.0` and 
`snowflake-connector-python=3.0.3`. However, version 3.0.0 of  
`snowflake-connector-python` bumped the pyarrow dependency from 
`>=8.0.0,<8.1.0` to `>=10.0.1,<10.1.0`. This results in a dependency resolution 
error when building a custom Airflow docker image. This only appears to happen 
when using the `pandas` compatible version of `snowflake-connector-python`
   
   ```
   #0 151.6 There are incompatible versions in the resolved dependencies:
   #0 151.6   pyarrow==9.0.0 (from -c 
https://raw.githubusercontent.com/apache/airflow/constraints-2.6.1/constraints-3.7.txt
 (line 470))
   #0 151.6   pyarrow>=3.0.0 (from db-dtypes==1.1.1->-c 
https://raw.githubusercontent.com/apache/airflow/constraints-2.6.1/constraints-3.7.txt
 (line 229))
   #0 151.6   pyarrow<10.1.0,>=10.0.1 (from 
snowflake-connector-python[pandas]==3.0.3->-c 
https://raw.githubusercontent.com/apache/airflow/constraints-2.6.1/constraints-3.7.txt
 (line 557))
   ```
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   When building the 2.6.1 Airflow image, if the dependencies include 
`snowflake-connector-python[pandas]`, a dependency incompatibility error is 
generated due to a mismatch required between pyarrow versions.
   
   ### Operating System
   
   Ubuntu 20.04 LTS
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to