Hi all,

https://github.com/apache/iceberg/pull/15095

We treat UUIDs inconsistently in the REST Catalog Spec. Some fields are
simple strings and others are a complex UUIDTypeValue with client-side
validations and strong descriptions. I'd like to change the spec so that
all UUID fields are treated as UUIDs instead of strings.

The additional context is critically important to tools in the OpenAPI
ecosystem (documentation + client library generators) that can't make
assumptions based on the field name.

This is not a breaking change, since these fields were always treated as
UUIDs server-side. The change is to make the spec reflect that reality.

Please let me know your thoughts.

Thank you!

-- Alex Stephen

Reply via email to