[
https://issues.apache.org/jira/browse/HDFS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478269#comment-16478269
]
Xiao Chen commented on HDFS-13281:
----------------------------------
Aha, my memory faded with this....
I was thinking about [this
comment|https://issues.apache.org/jira/browse/HDFS-13281?focusedCommentId=16419803&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16419803]
earlier. As far as this unit test is concerned, we should still write
encrypted bytes, right? Then you verify that the read bytes are encrypted.
My point is: even with the ability to write to raw, under no scenario should a
user write cleartext data to /.reserved/raw since that defeats the purpose of
encryption.
> Namenode#createFile should be /.reserved/raw/ aware.
> ----------------------------------------------------
>
> Key: HDFS-13281
> URL: https://issues.apache.org/jira/browse/HDFS-13281
> Project: Hadoop HDFS
> Issue Type: Sub-task
> 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.branch-2.patch,
> HDFS-13281.002.patch, HDFS-13281.003.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]
