0x1F as nested namespace separator for REST URL paths conflicts with Servlet spec

[westse]

Feature Request / Improvement

The current Iceberg REST spec uses 0x1F to separate the parts of a multipart (nested) namespace parameter in URL paths and elsewhere. However this conflicts with the Servlet spec which calls for rejecting control characters (encoded or not), including the unit separator (0x1F), as "suspicious" and to return 400. Servlet containers enforce this (e.g. see jetty/jetty.project#11495), making implementing the Iceberg REST spec difficult.

Should a different, or at least alternative, separator character be selected to avoid conflicting with the Servlet spec?

Query engine

None