-
Notifications
You must be signed in to change notification settings - Fork 415
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
Can't optimize a table created by Spark. #1648
Comments
I saw this, I didn't realize it was a regression and thought it was related to the code in that pull request 🤔 @wjones127 are you going to be fixing this or is it "up for grabs"? 😄 |
TBH I have no idea why this was in that PR. It doesn't have to do with upgrading PyArrow. Up for grab for now, as I'll try to fix #1602 first. |
So the optimize actually fails but not for that reason. The reproduction case has to be modified slightly (which I have in my branch), after which the error is:
which looks much more like a real problem |
The arrow schema that is being written has nanoseconds timestamps while microseconds is expected in the delta schema. Did somewhere the default got changed in pyarrow to NS unit? Also these errors could probably be easier to read if only the difference is shown instead of the full two schemas |
I hadn't had a chance to look deeper into this, good eye @ion-elgreco ! That means this is actually a test case for #1286! The reporter of that issue will be so happy to see this being worked on! |
Is there something similar on the rust side for this: https://arrow.apache.org/docs/python/generated/pyarrow.dataset.ParquetReadOptions.html#pyarrow.dataset.ParquetReadOptions.coerce_int96_timestamp_unit This is at least what I used to read spark-delta tables using Python bindings in delta-rs |
@rtyler people can avoid this error by writing tables with this spark setting. The annoying default is INT96.. |
Environment
Delta-rs version:
Binding:
Environment:
Bug
What happened:
https://github.com/delta-io/delta-rs/actions/runs/6243973257/job/16950202833?pr=1602
What you expected to happen:
How to reproduce it:
More details:
The text was updated successfully, but these errors were encountered: