[
https://issues.apache.org/jira/browse/HDFS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419803#comment-16419803
]
Rushabh S Shah commented on HDFS-13281:
---------------------------------------
{quote}I think at the minimum we should setxattr immediately after the file is
created.
{quote}
Exactly. I will add that functionality in HDFS-12597. The steps would be
something like this.
Webhdfs client will issue setXAttr after it issues {{create}} call to
_datanode_ and before it starts streaming encrypted data to datanode.
As you said that this just NN side change so I didn't incorporate that.
bq. One atomic way is perhaps pass in xattr at file creation time.
We did think that option also. Adding a new parameter {{FeInfo}} to create call.
If {{FeInfo}} is present, then namenode will use that FeInfo otherwise it will
generate new FeInfo but there was compatibility issue if namenode and datanode
is old but client is new and then it would double encrypt. So we threw away
that idea.
> Namenode#createFile should be /.reserved/raw/ aware.
> ----------------------------------------------------
>
> Key: HDFS-13281
> URL: https://issues.apache.org/jira/browse/HDFS-13281
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: encryption
> Affects Versions: 2.8.3
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Priority: Critical
> Attachments: HDFS-13281.001.patch, HDFS-13281.002.patch
>
>
> If I want to write to /.reserved/raw/<dir> and if that directory happens to
> be in EZ, then namenode *should not* create edek and just copy the raw bytes
> from the source.
> Namenode#startFileInt should be /.reserved/raw/ aware.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
