[
https://issues.apache.org/jira/browse/HDFS-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Lamb updated HDFS-6516:
-------------------------------
Attachment: HDFS-6516.001.patch
The .001 patch makes the list of encryption zones persistent. To achieve this,
when the edit log is loaded, if an OP_SET_XATTRS is seen, we check to see if
it's the special xattr which indicates that this is an encryption zone root. If
it is, then we add the directory to the FSNamesystem's list of all encryption
zones.
Image load time is slightly different. Since we maintain the list of encryption
zones using the pathname, we need the complete pathname of the directory. But
that may not be available since the image is still being loaded. If the INode
being loaded is an encryption zone root, then we stash that INode away and go
back to it at the end of image loading. At that point we get the full pathname
and add the encryption zone to the list of all of them.
> Implement List Encryption Zones
> -------------------------------
>
> Key: HDFS-6516
> URL: https://issues.apache.org/jira/browse/HDFS-6516
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: security
> Reporter: Charles Lamb
> Assignee: Charles Lamb
> Attachments: HDFS-6516.001.patch
>
>
> The list Encryption Zones command (CLI) and backend implementation
> (FSNamesystem) needs to be implemented. As part of this, the tests in
> TestEncryptionZonesAPI should be updated to use that to validate the results
> of the various CreateEZ and DeleteEZ tests.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
