catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg)

[mannerni]

Apache Iceberg version

1.10.0

Query engine

Trino

Please describe the bug 🐞

Hi, I was testing the interoperability of catalogs for read-write from different engines like trino & pyiceberg.
When a catalog is created using trino & iceberg rest catalog (i.e. its rest fixture docker image) the default catalog_name is set to = "rest_backend", whereas we can set the catalog name to user defined/configurable from pyiceberg.
We need ability to set/override the catalog_name in rest-fixture to allow access to catalog name that is created by say ex: pyiceberg or any other engine.
Can we have environment variable to set the catalog name, thereby interoperability can be enabled as one of the key desired use-case of Open Table Format?

Assuming this is the reference code associated to catalog name:
https://github.com/apache/iceberg/blob/main/open-api/src/testFixtures/java/org/apache/iceberg/rest/RESTCatalogServer.java#L101

CAHDATA: created from pyiceberg & rest_backend is set default in iceberg rest fixture.

Willingness to contribute

• I can contribute a fix for this bug independently
• I would be willing to contribute a fix for this bug with guidance from the Iceberg community
• I cannot contribute a fix for this bug at this time

[ebyhr]

Can we have environment variable to set the catalog name, thereby interoperability can be enabled as one of the key desired use-case of Open Table Format?

The catalogProperties variable comes from RCKUtils.environmentCatalogConfig() method. Could you please try CATALOG_CATALOG_NAME environment variable?

[mannerni]

Hi @ebyhr thanks for quick help.
I tried with CATALOG_CATALOG_NAME & was able to load/work with that catalog. Resolves my primiary need.
Since this catalog name is part of env var, this means single container instance of iceberg-fixture can load only 1 catalog. How can we load multiple catalogs at runtime. For example in pyiceberg we have .pyiceberg.yaml where we can configure multiple catalogs (though its staticcally pre-configured, not runtime), but once configured we can use those multiple catalog at runtime.
Please suggest if there are any ways, thanks!

[ebyhr]

@mannerni Trino doesn't support setting the catalog name at this time. I can send a PR once it's ready.

[mannerni]

Got it, thank you again for keeping posted.