[
https://issues.apache.org/jira/browse/HDFS-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-6391:
------------------------------
Attachment: hdfs-6391.003.patch
New patch attached. I just renamed the key-id constant. PBHelper, since these
are all required PB fields, they actually all need to be present. Checking for
the FEInfo itself being present is sufficient, and of course it's also checked
in FEInfo's constructor.
Some of these are also really nitty comments :) I fixed up the worst of FSDir's
imports, but I normally just let these go unless they're unused. FSDir was also
already inconsistent, and auto-format in my IDE moves a lot around. Some of
these finals also don't add much, since e.g. setFileEncryptionInfo is quite a
small function. I did it though.
> Get the Key/IV from the NameNode for encrypted files in DFSClient
> -----------------------------------------------------------------
>
> Key: HDFS-6391
> URL: https://issues.apache.org/jira/browse/HDFS-6391
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode, security
> Reporter: Alejandro Abdelnur
> Assignee: Andrew Wang
> Attachments: HDFS-6391.1.patch, hdfs-6391.002.patch,
> hdfs-6391.003.patch
>
>
> When creating/opening and encrypted file, the DFSClient should get the
> encryption key material and the IV for the file in the create/open RPC call.
> HDFS admin users would never get key material/IV on encrypted files
> create/open.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
