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

   ### Apache Iceberg version
   
   0.11.0 (latest release)
   
   ### Please describe the bug 🐞
   
   I am trying to connect to a rest catalog exposed by AWS S3 Tables as 
documented 
[here](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-open-source.html).
 The code snippet that I have is:
   `rest_catalog = load_catalog(
     catalog_name,
     **{
       "type": "rest",    
       "warehouse":"arn:aws:s3tables:<Region>:<accountID>:bucket/<bucketname>",
       "uri": "https://s3tables/.<Region>.amazonaws.com/iceberg",
       "rest.sigv4-enabled": "true",
       "rest.signing-name": "s3tables",
       "rest.signing-region": "<Region>"
     }
   rest_catalog.load_namespace_properties("my_namespace")
   )`
   
   However, I got an error:
   `1 validation error for NamespaceResponse
   properties
     Field required [type=missing, input_value={'namespace': ['my_namespace']}, 
input_type=dict]
       For further information visit https://errors.pydantic.dev/2.12/v/missing`
   
   I dug deeper into the [open api 
spec](https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml#L4146)
 for `GET /v1/{prefix}/namespaces/{namespace}` and looks like `properties` is 
**NOT** a required field in the response; hence, the response from AWS matches 
the specification. However, looks like the pydantic validation on iceberg side 
does not account for that. 
   
   Please let me know if I misunderstood something.
   
   ### 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
   - [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