Tangential question is about other identifiers like table names. E.g. Some catalogs support dots, others (like Unity) do not.
Thinking out loud: what if we mandate that lowercase and say underscores must be supported. The spec then escapes everything else (i.e. hex encoding including unicode) and asks the query engine to unescape what they can. But in APIs always the escaped variant is used. On Thu, Oct 9, 2025 at 2:35 PM Nicolae Vartolomei <[email protected]> wrote: > > 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
