ggershinsky commented on a change in pull request #32895:
URL: https://github.com/apache/spark/pull/32895#discussion_r650907224



##########
File path: docs/sql-data-sources-parquet.md
##########
@@ -252,6 +252,51 @@ REFRESH TABLE my_table;
 
 </div>
 
+## Columnar Encryption
+
+
+Since Spark 3.2, columnar encryption is supported for Parquet tables with 
Apache Parquet 1.12.
+
+Parquet uses the envelope encryption practice, where the file parts are 
encrypted with “data encryption keys” (DEKs), and the DEKs are encrypted with 
“master encryption keys” (MEKs). The DEKs are randomly generated by Parquet for 
each encrypted file/column. The MEKs are generated, stored and managed in a Key 
Management Service (KMS) of user’s choice. Parquet-test 
[package](https://repo1.maven.org/maven2/org/apache/parquet/parquet-hadoop/1.12.0/parquet-hadoop-1.12.0-tests.jar)
 has a mock KMS implementation that allows to run column encryption and 
decryption without a KMS server:
+
+<div class="codetabs">
+<div data-lang="scala"  markdown="1">
+{% highlight scala %}
+
+sc.hadoopConfiguration.set("parquet.encryption.kms.client.class" ,
+                           
"org.apache.parquet.crypto.keytools.mocks.InMemoryKMS")
+
+// Explicit master keys (base64 encoded) - required only for mock InMemoryKMS
+sc.hadoopConfiguration.set("parquet.encryption.key.list" ,
+                   "keyA:AAECAwQFBgcICQoLDA0ODw== ,  
keyB:AAECAAECAAECAAECAAECAA==")
+
+// Activate Parquet encryption, driven by Hadoop properties
+sc.hadoopConfiguration.set("parquet.crypto.factory.class" ,
+                   
"org.apache.parquet.crypto.keytools.PropertiesDrivenCryptoFactory")
+
+// Write encrypted dataframe files. 
+// Column "square" will be encrypted with master key "keyA".
+// Parquet file footers will be encrypted with master key "keyB"

Review comment:
       A good point! I'll change "encrypted with something like "protected".




-- 
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]

Reply via email to