[
https://issues.apache.org/jira/browse/HDFS-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129342#comment-16129342
]
Yongjun Zhang edited comment on HDFS-12295 at 8/16/17 8:12 PM:
---------------------------------------------------------------
Hi [~daryn],
Thanks a lot for your comments!
Good point about move etc operations. We can add that. For delete, the prefix
is like an no op. There quite some other operations, This change will become
cumbersome too.
What's your view about HDFS-12202? It doesn't need to change all the other
operations, but suggest to add a new set of API for getFileStatus and
listStatus. This is a hard sell too because we have to introduce the set of
APIs, and do dummy implementation for all FileSystems even if they don't care.
Would you please share your thoughts about this anyways?
Right now the only application is, distcp will decide whether to add the prefix
before calling getFileStatus and listStatus methods.
About the copy-n-paste, I did it as a quick dtraft to illustrate the idea for
discussion, will definitety put in more centralized location.
I'm not sure whether using super user to avoid consulting external permission
will work. Would you please see my discussion with [~chris.douglas] in
HDFS-12294?
Many Thanks.
was (Author: yzhangal):
Hi [~daryn],
Thanks a lot for your comments!
Good point about move etc operations. We can add that. For delete, the prefix
is like an no op. There quite some other operations, This change will become
ugly too.
What's your view about HDFS-12202? It doesn't need to change all the other
operations, but suggest to add a new set of API for getFileStatus and
listStatus. This is a hard sell too because we have to introduce the set of
APIs, and do dummy implementation for all FileSystems even if they don't care.
Would you please share your thoughts about this anyways?
Right now the only application is, distcp will decide whether to add the prefix
before calling getFileStatus and listStatus methods.
About the copy-n-paste, I did it as a quick dtraft to illustrate the idea for
discussion, will definitety put in more centralized location.
I'm not sure whether using super user to avoid consulting external permission
will work. Would you please see my discussion with [~chris.douglas] in
HDFS-12294?
Many Thanks.
> NameNode to support file path prefix /.reserved/bypassExtAttr
> -------------------------------------------------------------
>
> Key: HDFS-12295
> URL: https://issues.apache.org/jira/browse/HDFS-12295
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs, namenode
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
> Attachments: HDFS-12295.001.patch, HDFS-12295.001.patch
>
>
> Let NameNode to support prefix /.reserved/bypassExtAttr, so client can add
> thisprefix to a path before calling getFileStatus, e.g. /ab/c becomes
> /.reserved/bypassExtAttr/a/b/c. NN will parse the path at the very beginning,
> and bypass external attribute provider if the prefix is there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
