Apache Iceberg version
main (development)
Please describe the bug 🐞
I ran into this while integrating with the recent support for deletes because the deletion implementation uses the same scanning facilities which panic on a schema that includes a map<string, list<string>> field. I'm not entirely sure if it would not panic if all rows had full data in that field but since the field is nullable, it's possible and expected that some rows would have empty or null values.
I created a draft PR (not intended for merge but just for convenience) with the minimal reproduction test case showing the panic: #736.
Apache Iceberg version
main (development)
Please describe the bug 🐞
I ran into this while integrating with the recent support for deletes because the deletion implementation uses the same scanning facilities which panic on a schema that includes a
map<string, list<string>>field. I'm not entirely sure if it would not panic if all rows had full data in that field but since the field is nullable, it's possible and expected that some rows would have empty or null values.I created a draft PR (not intended for merge but just for convenience) with the minimal reproduction test case showing the panic: #736.