[
https://issues.apache.org/jira/browse/ORC-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854900#comment-16854900
]
Owen O'Malley commented on ORC-14:
----------------------------------
[[email protected]] the ORC change is completely contained in the ORC project.
It is a required property that no plugins are required for reading any ORC
files. A user needs to be able to read an ORC file that was written at another
site without asking for any plugins. Even more than that, the bytes in the file
have to be defined by the ORC specification to guarantee compatibility between
the implementations.
The integration of ORC column encryption into execution engines will be
trivial. For example, upgrading Spark to use column encryption will be very
easy with just needing to have the table properties set in the Hive MetaStore.
The one exception to this is Hive's LLAP, which is problematic. LLAP uses a lot
of ORC's internal classes that aren't in the API and thus is a lot more
sensitive to the changes under the hood.
It would be good to coordinate on a set of table property names so that moving
between Parquet and ORC will get equivalent protection.
> Add column level encryption to ORC files
> ----------------------------------------
>
> Key: ORC-14
> URL: https://issues.apache.org/jira/browse/ORC-14
> Project: ORC
> Issue Type: New Feature
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Major
> Attachments: columnEncryption.png
>
>
> It would be useful to support column level encryption in ORC files. Since
> each column and its associated index is stored separately, encrypting a
> column separately isn't difficult. In terms of key distribution, it would
> make sense to use an external server like the one in HADOOP-9331.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
