[
https://issues.apache.org/jira/browse/HDFS-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe Zhang updated HDFS-6987:
----------------------------
Target Version/s: (was: 2.6.0)
Affects Version/s: (was: 2.6.0)
Status: Patch Available (was: Open)
Submitting initial patch so we can review the basic logic. A few things need to
be addressed in the next patch:
# When getting the XAttr from the EZ, shall we read with or without snapshotID?
Since we are restricting that EZ level encryption info cannot change over its
life time, it seems we shouldn't just read XAttr from INode without snapshotID
# Need to add the logic to reject XAttr updates on EZ, so it doesn't get
accidentally changed
# [~tucu00] So {{FileEncryptionInfo}} should also be updated to include
{{keyName}} right? Just wanted to confirm before changing the class
> Move CipherSuite xattr information up to the encryption zone root
> -----------------------------------------------------------------
>
> Key: HDFS-6987
> URL: https://issues.apache.org/jira/browse/HDFS-6987
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: encryption
> Reporter: Andrew Wang
> Assignee: Zhe Zhang
> Attachments: HDFS-6987-20140917-v1.patch
>
>
> All files within a single EZ need to be encrypted with the same CipherSuite.
> Because of this, I think we can store the CipherSuite once in the EZ rather
> than on each file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
