You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "mannerni (via GitHub)" <gi...@apache.org> on 2026/01/06 07:38:22 UTC
[I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
mannerni opened a new issue, #14972:
URL: https://github.com/apache/iceberg/issues/14972
### 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.
<img width="638" height="142" alt="Image" src="https://github.com/user-attachments/assets/ff569ce8-5965-444c-a090-910b64b11d83" />
### 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
- [x] I cannot contribute a fix for this bug at this time
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
Posted by "ebyhr (via GitHub)" <gi...@apache.org>.
ebyhr commented on issue #14972:
URL: https://github.com/apache/iceberg/issues/14972#issuecomment-3722069302
@mannerni Trino doesn't support setting the catalog name at this time. I can send a PR once it's ready.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
Posted by "mannerni (via GitHub)" <gi...@apache.org>.
mannerni commented on issue #14972:
URL: https://github.com/apache/iceberg/issues/14972#issuecomment-3722399600
Got it, thank you again for keeping posted.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
Posted by "ebyhr (via GitHub)" <gi...@apache.org>.
ebyhr commented on issue #14972:
URL: https://github.com/apache/iceberg/issues/14972#issuecomment-3716581774
> 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?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu closed issue #14972: catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg)
URL: https://github.com/apache/iceberg/issues/14972
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
Posted by "mannerni (via GitHub)" <gi...@apache.org>.
mannerni commented on issue #14972:
URL: https://github.com/apache/iceberg/issues/14972#issuecomment-3721987692
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!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] catalog_name is hardcode in rest fixture, causing interoperability issue (with trino & pyiceberg) [iceberg]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #14972:
URL: https://github.com/apache/iceberg/issues/14972#issuecomment-4411035463
I was able to verify that `CATALOG_CATALOG_NAME=mywarehouse` is indeed the env var to set to override `catalog.name`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org