You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Given a nested list, indexing works correctly as long as the index is not 0 or larger than the size of the list. However, if 0 or an index larger than the list is given, it will throw an error similar to the following:
Error: Arrow error: Invalid argument error: column types must match schema types, expected Float64 but found List(Field { name: "item", data_type: Float64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }) at column index 1
Describe the bug
Given a nested list, indexing works correctly as long as the index is not 0 or larger than the size of the list. However, if 0 or an index larger than the list is given, it will throw an error similar to the following:
To Reproduce
Use the attached parquet file, list.parquet.gz
This Parquet file contains a single row of data as follows:
Example code that demonstrates the bug (after uncompressing the file):
Expected behavior
We expect to get a null value when the index is out of range. For example, the above code should produce the following output:
Additional context
We should be able to index this correctly, and if an invalid index is given, that should return nulls. Example:
This should produce the following output:
The text was updated successfully, but these errors were encountered: