[
https://issues.apache.org/jira/browse/HDFS-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126000#comment-16126000
]
Daryn Sharp commented on HDFS-12295:
------------------------------------
If this is to be implemented, which I'm not sure it should be, having only a
subset of operations understand the path prefix is too fragile and creates
semantic inconsistencies. Ex. getFileStatus on
/.reserved/bypassExtAttr/dir/file effectively operates on /dir/file; however
delete, rename, etc operates on /.reserved/bypassExtAttr/dir/file. That's a
showstopper.
Copy-n-paste of the same chunk of code should be a red flag that something is
wrong and it needs to be implemented in a more centralized location.
I'd almost rather the use case be handled via the superuser not being subject
to the external permissions.
> 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: [email protected]
For additional commands, e-mail: [email protected]
