-
Notifications
You must be signed in to change notification settings - Fork 102
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
Getting signed integer is greater than maximum error when querying large table #414
Comments
https://stackoverflow.com/questions/70905872/overflowerror-when-reading-from-s3-signed-integer-is-greater-than-maximum Please check the following section of the README for usage of the chunksize option. |
Hey @laughingman7743 I do believe it is related to Python not to pyathena. I will try the links you mentioned and close the issue if it will solve my problem. |
Hey @laughingman7743 Unfortunately, the chunksize didn't work either.
I will investigate more tomorrow and post the updates here. |
PyAthena==1.11.3 🤔 |
Yup, the code I took ownership of is a bit old, so I decided to update the dependencies. But I got that error. |
When I query a large table (about 5 million rows), I get this error:
pyathena.error.OperationalError: signed integer is greater than maximum
Here is the code I am using:
This is the output I get:
My dependencies:
Further info:
The table contains 15 columns, most of them are with timestamps and strings values.
The column with timestamps contains unix format timestamps and '
NOT APPLICABLE
' when the value is empty.I was not getting this issue with lower versions of pyathena and pandas. But I had to update them due to vulnerabilities.
Do you know how to fix this?
Or how to query the table in chunks then merge them?
The text was updated successfully, but these errors were encountered: