-
Notifications
You must be signed in to change notification settings - Fork 100
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
PyArrow version requirement #55
Comments
I have a similar issue but personally I'm interested in using pyarrow |
@Tom-Newton pyarrow @YS-L I'll look into reducing our pyarrow specificaiton. I think we landed on version 9 because it was the latest at the time we wrote the connector. |
Thanks @susodapop 🙂 . With 2.2.1 my pyarrow problem is solved but now numpy is an issue. We are on numpy We are currently using |
I want to make this work for you but I also can't reproduce your installation problem. For your info: note that our specific requirements were dictated by Poetry so we haven't deliberately excluded anyone and thus far our tests run automatically on Python 3.7-3.11 without issues. You're welcome to open a pull request that modifies |
I created a PR #74. It needs a review and for someone to approve running the build checks. |
@susodapop please could you approve running the github workflows |
Done! |
Hello! Is the version requirement on the pyarrow package strict?
We would like to use
databricks-sql-python
in a project that depends on a lower version of pyarrow (8.0.0). We ran into conflicting version issues when using package management tools such as poetry. In our tests it seemsdatabricks-sql-python
can work with older versions of pyarrow such as 8.0.0. It would be great ifdatabricks-sql-python
can specify a wider range of pyarrow versions for better compatibility.The text was updated successfully, but these errors were encountered: