You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/03/30 10:40:00 UTC

[jira] [Commented] (PARQUET-1659) Add AES-CTR to Parquet Encryption

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

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

pitrou commented on pull request #153:
URL: https://github.com/apache/parquet-format/pull/153#issuecomment-810115525


   There doesn't seem to have been any activity around this (or the attached JIRA) since September 2019. @ggershinsky Do you think it is worthwhile keeping this open?


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


> Add AES-CTR to Parquet Encryption 
> ----------------------------------
>
>                 Key: PARQUET-1659
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1659
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-cpp, parquet-format, parquet-mr
>    Affects Versions: format-2.6.0
>            Reporter: Xinli Shang
>            Priority: Minor
>              Labels: pull-request-available
>
> AES-GCM-CTR perform GCM encryption on metadata and CTR encryption on data.
> AES-CTR would perform CTR encryption on both. 
> During Perf testing, we found AES-CTR can improve read/write performance by ~10% comparing with AES-GCM-CTR.
>  
> I checked with Gidon and the initial assumption was that AES-GCM-CTR would have similar performance as AES-CTR. But with recent performance benchmarking, we found it is worthy to introduce AES-CTR. Since many companies strive for parquet performance improvement. 
>  



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