Neuw84 opened a new issue, #1449:
URL: https://github.com/apache/iceberg-python/issues/1449

   ### Apache Iceberg version
   
   0.8.1 (latest release)
   
   ### Please describe the bug 🐞
   
   Hi, 
   
   I am trying to read and write from a RMS (Redshift Managed Storage) backed 
catalog on AWS. The thing is that I am trying configuring the REST catalog like 
this. 
   
   ```
   rest_catalog = load_catalog(
       "rms-demo.dev",
       **{
           "type": "rest",
           "uri": "https://glue.us-east-2.amazonaws.com/iceberg";,
                "rest.sigv4-enabled": "true",
                  "rest.signing-name": "glue",
                  "rest.signing-region": "us-east-2"
       }
   )
   ```
   
   But the thing is that the calls to the catalog goes through the default 
account id catalog. **Note the http call on the traceback**.   it should be 
showing "rms-demo.dev" on the url and instead is using the accountId. 
   
   ```
   Traceback (most recent call last):
     File 
"/home/ec2-user/my_env/lib64/python3.9/site-packages/pyiceberg/catalog/rest.py",
 line 599, in _create_table
       response.raise_for_status()
     File 
"/home/ec2-user/my_env/lib64/python3.9/site-packages/requests/models.py", line 
1024, in raise_for_status
       raise HTTPError(http_error_msg, response=self)
   requests.exceptions.HTTPError: 404 Client Error: Not Found for url: 
https://glue.us-east-2.amazonaws.com/iceberg/v1/catalogs/accountId/namespaces/public/tables
   
   The above exception was the direct cause of the following exception:
   ```
   
   There is something in backend scenes on why it is injecting the aws account 
instead of using the catalog name?
   
   Thanks!!
   
   ### Willingness to contribute
   
   - [ ] I can contribute a fix for this bug independently
   - [X] 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


-- 
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