Hi there,

I noticed the Iceberg specification doesn't address column name case
sensitivity. I encountered an issue where Glue Iceberg REST converts a
column named "Foo" to lowercase, which affects other processes relying on
case-sensitive column name matching.

While Iceberg may not explicitly manage collisions, Glue does. This leads
to errors when creating columns like "Foo" and "foo" in the same table due
to perceived collisions.

I suggest the Iceberg specification include guidance on how implementers
should handle column name case sensitivity.

What do you think?

Nicolae

Reply via email to