[ 
https://issues.apache.org/jira/browse/HDFS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420553#comment-16420553
 ] 

Rushabh S Shah commented on HDFS-13281:
---------------------------------------

{quote}Could you write a design doc elaborating all these, and add to the 
umbrella jira?
{quote}
Sure when I start working on HDFS-12597 (in about a week), writing a design doc 
would be the first thing I will do.
I am sorry that even you asking me multiple times on HDFS-12574, I didn't get 
enough cycles to write a design doc.
I will find cycles for that and will have write up on that jira also.

bq.  Please add necessary links. I'd think this as a subtask of HDFS-12355 and 
required by HDFS-12597.
Added necessary links.

As always test failures are not related to this patch.

[~xiaochen]: Is there anything you expect me to change in the latest trunk 
patch ?
The trunk patch doesn't apply cleanly to branch-2 due to some import changes.
Attached a branch-2 (which pplies to branch-2.8 also)


> 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
>
>
> 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]

Reply via email to