-
Notifications
You must be signed in to change notification settings - Fork 419
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
Rust Engine write_deltalake Schema #2200
Comments
Okay i dont think this is a bug now i have unpicked it further, the timestamp field type is written to delta as an EPOCH timestamp, as such fields of type timestamp expect the time stamp field to be an integer and by default in microseconds. I have updated my code to handle this scenario by setting any pyarrow timestamp fields to seconds using the below logic on initialisation,
Then during even processing changing the timestamp field to posix time using datetime.timestamp() with below code logic
|
@tastyfrankfurt I do believe we are missing a case here, you passed a schema but we are not using it when writing with Rust engine, I'll try to address this |
No worries, i guess the issue now for us if i have moved some data processing back into the python code base which i didn't want to do for performance reasons, anyway, i look forward to seeing what you can find. |
Closing this since passing a schema is not really needed. Can always cast beforehand |
Environment
Ubuntu 22.04, python3, reading events from Azure eventhubs and writing out to Azure blob storage.
Delta-rs version:
pip list returns version 0.15.3 for delta lake
Binding:
Environment:
Bug
What happened:
When using schema option on the write_deltalake function with the rust engine it fails to write out to delta lake on azure storage.
If i change to pyarrow engine then it works as expected.
What you expected to happen:
When using schema option on the write_deltalake function with the rust engine it writes out to delta lake on azure storage.
How to reproduce it:
Use the code sample as stated below,
Apologies for my code snippet if there are any errors.
More details:
BACKTRACEFULL.txt
The text was updated successfully, but these errors were encountered: