Non uniform behavior of AUTHORIZATION options in Iceberg REST catalog

[drnta]

We are using Trino with Iceberg catalog and iceberg.catalog.type=rest.

When the user executes any ALTER <something> SET AUTHORIZATION <something>; the query fails with

(someMethod) is not supported for Iceberg REST catalog

as expected since TrinoRestCatalog implementation does not support corresponding methods for now.

However when the similar option is used in CREATE NAMESPACE statement like CREATE NAMESPACE AUTHORIZATION <something>; the query executes successfully and TrinoRestCatalog#createNamespace just silently ignores the TrinoPrincipal owner.
This can be misleading a bit since the query executes successfully but the passed option makes no effect in fact.

It can be more uniform and clear if TrinoRestCatalog would also throw the NOT_SUPPORTED exception in case when AUTHORIZATION option was explicitly passed to the CREATE NAMESPACE statement since as for now AUTHORIZATION management is not supported by Iceberg REST catalog implementation.

Thanks.