feat: Dynamic Parquet encryption and decryption properties #16779
+1,031
−68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
See #16778. This allows per-file encryption key generation and for keys to be retrieved based on encryption metadata stored in the Parquet files, rather than readers needing to know AES keys upfront.
What changes are included in this PR?
EncryptionFactorytrait for types that generate file encryption and decryption properties. This is loosely based on the approach used by Spark (see this comment for details).EncryptionFactoryinstances in theRuntimeEnv, similar to howObjectStores can be registered.cryptoconfiguration field inTableParquetOptionsto allow setting an encryption factory id, and opaque configuration options required by the encryption factory.EncryptionFactorywhere necessary.Are these changes tested?
Yes, new unit tests and an example have been added.
Are there any user-facing changes?
Yes, this is a new user-facing feature.