Open asfimport opened 1 year ago
&res / @0x26res: As a general comment, it is quiet easy to create data that is not valid in terms of nullability in arrow. In the example above I was able to create a table where the nullability of the fields is not respected.
And, this would pass:
table.validate(full=True)
But this would throw ArrowInvalid:
table.cast(table.schema)
I'm saving an arrow table to parquet. One column is a list of structs, which elements are marked as non nullable. But the data isn't valid because I've put a null in one of the nested field.
When I save this data to parquet and try to load it back I get a very misleading message:
I would rather arrow complains when creating the table or when saving it to parquet.
Here's how to reproduce the issue:
Reporter: &res / @0x26res
Note: This issue was originally created as ARROW-18439. Please see the migration documentation for further details.