adnanhemani commented on PR #1424: URL: https://github.com/apache/polaris/pull/1424#issuecomment-2845711209
> I know there is some churn in the encryption configuration in Iceberg, but I also know that s3.sse.key is a property that's currently used to specify the KMS key associated with a table. The way I read [this](https://iceberg.apache.org/docs/1.6.0/aws/#s3-server-side-encryption), I believe the `s3.sse.key` property is on the catalog rather than the table - and I don't see this key being persisted in the [table metadata either](https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/TableMetadata.java). I'm not an Iceberg expert, but I'm guessing that won't be right to do since the user can change this input in their session and we would not know if they can have access to this KMS key from the session itself? -- 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: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
