You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Chris McFarland (JIRA)" <ji...@apache.org> on 2016/10/27 17:28:58 UTC

[jira] [Commented] (AVRO-1372) Avro file data encryption for Java

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

Chris McFarland commented on AVRO-1372:
---------------------------------------

I know Avro is touted as a good data format for Kafka records (and I'm considering Avro for that purpose), so I would say it's more appropriate to configure at the Avro level to keep the component loosely coupled with its applications. If you guys add encryption, then I'm going straight to Avro! If not, then I can't use it (or I have to roll my own).

> Avro file data encryption for Java 
> -----------------------------------
>
>                 Key: AVRO-1372
>                 URL: https://issues.apache.org/jira/browse/AVRO-1372
>             Project: Avro
>          Issue Type: Sub-task
>          Components: java
>    Affects Versions: 1.8.0
>            Reporter: Jerry Chen
>              Labels: Rhino
>         Attachments: AVRO-1372.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> For Java, Avro has already support of compressions such as deflate or snappy based on its own codec infrastructure. To support encryption, this work needs to extend the codec infrastructure with the ability to handle codec context such as the encryption keys. The reader and writer needs to be extended for context handling as well. Also AES codec will be implemented as the default encryption codec.
> To keep the compatibility of the reader and writer, new constructor and methods with codec context can be added instead of modifying the existing methods. Although there are other ways for passing in the codec context such as using thread local or system properties, these methods are easier to cause problems, not direct and not self explaining at the API level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)