[
https://issues.apache.org/jira/browse/PARQUET-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221434#comment-17221434
]
ASF GitHub Bot commented on PARQUET-1396:
-----------------------------------------
shangxinli commented on a change in pull request #808:
URL: https://github.com/apache/parquet-mr/pull/808#discussion_r512690615
##########
File path: parquet-common/pom.xml
##########
@@ -67,6 +67,7 @@
<artifactId>audience-annotations</artifactId>
<version>0.12.0</version>
</dependency>
+
Review comment:
fixed
----------------------------------------------------------------
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:
us...@infra.apache.org
> Example of using EncryptionPropertiesFactory and DecryptionPropertiesFactory
> ----------------------------------------------------------------------------
>
> Key: PARQUET-1396
> URL: https://issues.apache.org/jira/browse/PARQUET-1396
> Project: Parquet
> Issue Type: New Feature
> Components: parquet-mr
> Affects Versions: 1.10.0, 1.10.1
> Reporter: Xinli Shang
> Priority: Major
> Labels: pull-request-available
>
> This JIRA is an extension to Parquet Modular Encryption Jira(PARQUET-1178)
> that will provide the basic building blocks and APIs for the encryption
> support.
> This JIRA provides a crypto data interface for schema activation of Parquet
> encryption and serves as a high-level layer on top of PARQUET-1178 to make
> the adoption of Parquet-1178 easier, with pluggable key access module,
> without a need to use the low-level encryption APIs. Also, this feature will
> enable seamless integration with existing clients.
> No change to specifications (Parquet-format), no new Parquet APIs, and no
> changes in existing Parquet APIs. All current applications, tests, etc, will
> work.
> From developer perspective, they can just implement the interface into a
> plugin which can be attached any Parquet application like Hive/Spark etc.
> This decouples the complexity of dealing with KMS and schema from Parquet
> applications. In large organization, they may have hundreds or even thousands
> of Parquet applications and pipelines. The decoupling would make Parquet
> encryption easier to be adopted.
> From end user(for example data owner) perspective, if they think a column is
> sensitive, they can just set that column’s schema as sensitive and then the
> Parquet application just encrypt that column automatically. This makes end
> user easy to manage the encryptions of their columns.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
