[ https://issues.apache.org/jira/browse/HDFS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419067#comment-16419067 ]
Rushabh S Shah commented on HDFS-13281: --------------------------------------- {quote} Because reading /.reserved/raw is supposed to be returning the raw bytes, shouldn't encryptedReservedStream be different than unEncryptedBytes? {quote} Forgot to address this in last comment. Since the client is writing directly to {{/.reserved/raw}} path, it is client's responsibility to encrypt the data and call {{setXAttr}} to set {{FEInfo}}. In test case, I didn't set that raw attribute so the raw bytes and decrypted bytes are the same. > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org