You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need pyarrow 17 in one of our projects, because of other dependency constraints. However, we also need 3.3.0, because we are facing unstable database connections with this library's version < 3. So it'd be lovely to relax the dependency on Pyarrow < 17 to include the latest stable version of 17.
Reacted by repied, arredond, Shantanu and Michi Platzer
I see the fix here is to move to pyarrow<18.0 as the upper bound. Would you consider not adding an upper bound at all? Upper bounds really make dependency management much, much harder for complex projects.
The pyarrow requirement no longer has an upper bound: the latest release (4.8.0) requires pyarrow>=14.0.1 on Python 3.10–3.12 (with higher floors on 3.13/3.14), via the pyarrow extra. Installing databricks-sql-connector[pyarrow] on Python 3.12 resolves pyarrow 26.0.0, and Arrow-backed fetches work with it. Closing.
Activity
arredond commentedon Oct 4, 2024
(copying over from the PR comments)
I see the fix here is to move to pyarrow<18.0 as the upper bound. Would you consider not adding an upper bound at all? Upper bounds really make dependency management much, much harder for complex projects.
Here's a nice discussion on the topic.
Also, I see this has already been a problem for other users in the past: #389 , #390 , #55
vuanhphung commentedon Oct 29, 2026
The pyarrow requirement no longer has an upper bound: the latest release (4.8.0) requires
pyarrow>=14.0.1on Python 3.10–3.12 (with higher floors on 3.13/3.14), via thepyarrowextra. Installingdatabricks-sql-connector[pyarrow]on Python 3.12 resolves pyarrow 26.0.0, and Arrow-backed fetches work with it. Closing.