johnclara edited a comment on pull request #2444: URL: https://github.com/apache/iceberg/pull/2444#issuecomment-816982342
How would you recommend storing the key materials associated with the metadata file? (for example the kmsid of the key used to encrypt the TableMetadata file?) I was thinking one option would be along side the TableMetadata location within the external metastore for the active snapshot, and then within the TableMetadata for previous snapshots? For instance my team uses DynamoDB as an external catalog with schema: `icebergTableName, metadataLocation` We could add another column: `icebergTableName, metadataLocation, keyMaterials` For loading the current snapshot of the table, we could use the key materials within the external metastore to read the TableMetadata file. In order to look at previous snapshots, the keyMaterials could be stored along side the metadataLocation in the previous snapshots section of the TableMetadata file. https://github.com/apache/iceberg/blob/master/core/src/test/resources/TableMetadataV2Valid.json#L85 -- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
