[jira] [Commented] (PARQUET-1396) Cryptodata Interface for Schema Activation of Parquet Encryption

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PARQUET-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048714#comment-17048714 ] 

ASF GitHub Bot commented on PARQUET-1396:
-----------------------------------------

shangxinli commented on pull request #764: PARQUET-1396: Cryptodata Interface for Schema Activation of Parquet E…
URL: https://github.com/apache/parquet-mr/pull/764
 
 
   …ncryption
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Parquet Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references them in the PR title. For example, "PARQUET-1234: My Parquet PR"
     - https://issues.apache.org/jira/browse/PARQUET-XXX
     - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain Javadoc that explain what it does
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


> Cryptodata Interface for Schema Activation of Parquet Encryption
> ----------------------------------------------------------------
>
>                 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)