Feature Request / Improvement
Following #1028, it took a bit of digging to figure out how to connect pyiceberg to Nessie using the S3V4RestSigner.
Eventually I was helped in both communities to find that pyiceberg defaults to setting X-Iceberg-Access-Delegation: vended-credentials, which means that Nessie will not supply the s3.signer information in the resulting io properties.
This header is not documented anywhere in the pyiceberg docs; although I was very glad to see there was already the ability to override headers in the client config. At the very least, there should be some documentation for this, and ideally some way to remove the default header, i.e. allowing the catalog to decide how it wants to respond.
Feature Request / Improvement
Following #1028, it took a bit of digging to figure out how to connect pyiceberg to Nessie using the S3V4RestSigner.
Eventually I was helped in both communities to find that pyiceberg defaults to setting
X-Iceberg-Access-Delegation: vended-credentials, which means that Nessie will not supply thes3.signerinformation in the resulting io properties.This header is not documented anywhere in the pyiceberg docs; although I was very glad to see there was already the ability to override headers in the client config. At the very least, there should be some documentation for this, and ideally some way to remove the default header, i.e. allowing the catalog to decide how it wants to respond.