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

Gidon Gershinsky commented on PARQUET-1792:
-------------------------------------------

There is also a security aspect. While "prune" cleanly removes a sensitive 
column, and therefore is safe - "mask"/"redact" replaces one version of the 
column data with another version, and can easily leak sensitive information if 
not done properly.  I believe that at this stage, its best done above Parquet - 
by the users, who can simply add columns with the masked data. It can be also 
faster than Parquet tools, if run on a multi-threaded engine, as mentioned by 
Gabor.

We're working on a system that would allow to analyze Parquet files with 
masked/redacted columns, and detect information leakage. This would also allow 
to perform masking inside Parquet libraries, making it fast / multi-threaded. 
But this project will take a while to complete. It's not urgent though, since, 
again, masking/redaction can be easily implemented by the users today, above 
Parquet. 

> Add 'mask' command to parquet-tools/parquet-cli
> -----------------------------------------------
>
>                 Key: PARQUET-1792
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1792
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-mr
>    Affects Versions: 1.12.0
>            Reporter: Xinli Shang
>            Assignee: Xinli Shang
>            Priority: Major
>             Fix For: 1.12.0
>
>
> Some personal data columns need to be masked instead of being 
> pruned(Parquet-1791). We need a tool to replace the raw data columns with 
> masked value. The masked value could be hash, null, redact etc.  For the 
> unchanged columns, they should be moved as a whole like 'merge', 'prune' 
> command in Parquet-tools. 
>  
> Implementing this feature in file format is 10X faster than doing it by 
> rewriting the table data in the query engine. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to