Skip to content
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

zlib failure in PyArrow 0.11.0 #2756

Closed
amachanic opened this issue Oct 14, 2018 · 8 comments
Closed

zlib failure in PyArrow 0.11.0 #2756

amachanic opened this issue Oct 14, 2018 · 8 comments

Comments

@amachanic
Copy link

The following produces an exception on PyArrow 0.11.0: "zlib deflate failed, output buffer too small"

It works fine on 0.10.0, so I assume this is a regression?

import io
import pyarrow
from pyarrow import parquet

tbl = pyarrow.Table.from_arrays([pyarrow.array(['abc', 'def'])], ['some_col'])

f = io.BytesIO()
parquet.write_table(tbl, f, compression='gzip')
@kszucs
Copy link
Member

kszucs commented Oct 14, 2018

Although I can't reproduce it, the error must come from here.

How did You install pyarrow? Which platform?
Could You please create a JIRA ticket instead?

@wesm
Copy link
Member

wesm commented Oct 14, 2018

I think we are dynamically linking to zlib now in 0.11 so @amachanic could you let us know what other versions of zlib do you have installed on your system?

@amachanic
Copy link
Author

@kszucs I installed pyarrow via pip. I had initially tested this on Amazon Linux (which I guess is Red Hat). Just tested on a couple of other machines: CentOS 7, and Ubuntu 16.04, and the repro works (which is to say, throws an exception) on both. I also just tested on Windows 7, and the repro does NOT throw an exception there.

Happy to create a JIRA ticket.

@wesm: both the Amazon Linux and CentOS machines have zlib 1.2.7-17. On Ubuntu, looks like it's 1.2.8 -- but full disclosure, I'm not sure I checked properly there. And I'm not sure at all how to check on Windows.

@amachanic
Copy link
Author

JIRA ticket here. Thank you for your attention to this issue.

@tsellers-r7
Copy link

tsellers-r7 commented Oct 18, 2018

It looks like the fix landed 2 days ago. Is there a projected date for when the code will be released and show up on PyPi?

Thanks.

@wesm
Copy link
Member

wesm commented Oct 18, 2018

We need to release 0.11.1. I am going to work on that today; so reckon updated packages would be on PyPI within the next 96 hours or so

@wesm wesm closed this as completed Oct 18, 2018
@amachanic
Copy link
Author

@wesm many thanks!

@xhochy
Copy link
Member

xhochy commented Oct 27, 2018

The fix was uploaded on PyPI some days ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants