kevinjqliu commented on PR #4039: URL: https://github.com/apache/iceberg-python/pull/4039#issuecomment-6407026456
BTW I had my agent check against the source code of other catalogs. Only Lakekeeper and Nessie support S3 remote signing; Polaris and Gravitino don't support it at all. And only Lakekeeper reads the body, so the PR fixes deletes for Lakekeeper and makes no difference to Nessie, which ignores the field. | Catalog | Remote signing? | Effect of this PR | | --- | --- | --- | | **Lakekeeper** | Yes. It parses the `DeleteObjects` XML and checks each key is inside the table location; with no body it rejects the request (`DeleteWithoutBody`). | **Required**, as confirmed by our local run. | | **Nessie** | Yes. `IcebergS3SignParams` accepts an optional `body` and passes it to its signer if present. Authorization only checks the request URI against the table's locations. It never parses the delete keys. | No change. Nessie accepts the body as an optional field and ignores it. | | **Polaris** | No. The S3 request-signing PRs (apache/polaris#2280, apache/polaris#3995) were closed without merging. A merged change (apache/polaris#5473) only clarified the error message for "unsupported remote signing". A feature request (apache/polaris#32) is still open. | None today. | | **Gravitino** | No. Its Iceberg REST docs say "`remote-signing`: Gravitino doesn't support this mode yet". It only does credential vending. | None. | -- 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]
