You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Lance Dacey (Jira)" <ji...@apache.org> on 2021/01/27 23:44:00 UTC
[jira] [Closed] (ARROW-11390) [Python] pyarrow 3.0 issues with
turbodbc
[ https://issues.apache.org/jira/browse/ARROW-11390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lance Dacey closed ARROW-11390.
-------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
I reorganized my Dockerfile to ensure that pyarrow 3.0 was installed before turbodbc (there was a base image which was installing 2.0), and I believe that conda-forge was updated for turbodbc as well
> [Python] pyarrow 3.0 issues with turbodbc
> -----------------------------------------
>
> Key: ARROW-11390
> URL: https://issues.apache.org/jira/browse/ARROW-11390
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
> Affects Versions: 3.0.0
> Environment: pyarrow 3.0.0
> fsspec 0.8.4
> adlfs v0.5.9
> pandas 1.2.1
> numpy 1.19.5
> turbodbc 4.1.1
> Reporter: Lance Dacey
> Priority: Major
> Labels: python, turbodbc
> Fix For: 3.0.0
>
>
> This is more of a turbodbc issue I think, but perhaps someone here would have some idea of what changed to cause potential issues.
> {code:java}
> cursor = connection.cursor()
> cursor.execute("select top 10 * from dbo.tickets")
> table = cursor.fetchallarrow(){code}
> I am able to run table.num_rows and it will print out 10.
> If I run table.to_pandas() or table.schema or try to write the table to a dataset, my kernel dies with no explanation. I reverted back to pyarrow 2.0 and the same code works again.
> [https://github.com/blue-yonder/turbodbc/issues/289]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)