-
Notifications
You must be signed in to change notification settings - Fork 16
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
failed to map column projection- incompatible data types list field element vs item #31
Comments
Thanks for the feedback! I've seen this issue pop up in the past datafusion-contrib/datafusion-catalogprovider-glue#4 (comment) but it fell off my radar... Seems that this could use a bit more investigation.. |
When I find some time this could help in tracing back the mismatch: https://arrow.apache.org/blog/2022/10/17/arrow-parquet-encoding-part-3/ |
@timvw I found the documentation for
|
I have a table that reads correctly using Spark + Delta Lake Libraries, but I'm having trouble reading via
pv
.do you know which downstream dependency could be giving me this error?
I checked the schema from the delta transaction log and didn't see a hardcoded
item
orelement
:When I look at the schema of a sample parquet file on s3, I do indeed see that the item in the list is called
element
:I see this exact error is from here: https://github.com/apache/arrow-datafusion/blob/aad82fbb32dc1bb4d03e8b36297f8c9a3148df89/datafusion/core/src/physical_plan/file_format/mod.rs#L253
And I also see that
element
is hardcoded in delta-rs here:https://github.com/delta-io/delta-rs/blob/83b8296fa5d55ebe050b022ed583dc57152221fe/rust/src/delta_arrow.rs#L38-L48 (pr: delta-io/delta-rs#228)
But I can't seem to find where the schema mismatch is coming from.
The text was updated successfully, but these errors were encountered: