[
https://issues.apache.org/jira/browse/HDFS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414757#comment-16414757
]
Xiao Chen commented on HDFS-13281:
----------------------------------
Thanks for working on this [~shahrs87].
Could you provide some background? Is this required for the webhdfs work?
Please link it if so.
I'm a bit nervous on supportability, because it would be hard to tell whether a
file without FileEncryptionInfo in an EZ is due to a bug or due to it's written
this way. Currently it's always a bug. Re-encryption can still work but each
file without feInfo leads to a warn message, we should check if there are any
similar assumptions / checks else where in HDFS.
> 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
>
>
> 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
