Hi all, When I was using the SupportsNamespaces to do the namespace create and exists check with other catalog services that implement the Iceberg REST API, I found it has different results with different catalog services. Iceberg has provided a standard API to do the namespace operations, but seems iceberg does not have a standard spec on the REST API implementation. That makes the other catalog services implement differently and then breaks the SupportsNamespace interface usage.
Do you think iceberg needs to standardize the REST spec to make sure the logic is the same for using the SupportsNamespace interface? Otherwise, the SupportsNamespace interface is meaningless because the client needs to handle different logic to create a namespace or other operations when using different catalog. For example, Nessie doesn't support auto-creating parent namespace: https://github.com/apache/iceberg/pull/10630 But the JDBC catalog supports it. Thanks. Yong
