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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to