Daryn Sharp commented on HDFS-13281:

{quote}The argument is the test should verify the encrypted bytes written are 
still encrypted bytes.
Whether it's "encrypted" is irrelevant though.  There's already tests for 
read/write to raw so I'd say testing file contents is beyond the scope of this 
{quote}The whole point of this jira is namenode _will not_ create an edek if we 
write to {{/.reserved/raw}} path.
Correct.  How about we end the debate by just creating the file and verifying 
no edek is present?

> 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

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to