Hi folks, The REST spec doesn't explicitly state how field `id`s should be handled by a catalog server. Questions have been raised in the community around field id handling behavior in the past [1] [2], so I think it is worth clarifying in the spec.
A good example of the intended difference in behavior is that `CreateTableRequest` reassigns field IDs, whereas `AddSchemaUpdate` preserves the field IDs provided by the client (in the Iceberg reference implementation). I'm hoping this clarification makes it easier for REST spec implementations to handle these requests in a way that keeps their table state consistent. I'd appreciate your review: https://github.com/apache/iceberg/pull/17137 Sung [1] https://lists.apache.org/thread/kwfy80s2nm6xcpohkrzznsmhqsmz32c3 [2] https://github.com/apache/iceberg/issues/13164
