[
https://issues.apache.org/jira/browse/HDFS-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965151#comment-16965151
]
Wei-Chiu Chuang edited comment on HDFS-14802 at 11/1/19 11:20 PM:
------------------------------------------------------------------
Unrelated.
It's unfortunate the configuration is listed in core-default.xml and named as
fs.protected.directories.
It should have been named as dfs.name.xxxx, since it's only valid for HDFS.
IMO we need another jira to deprecate the config and move it to
hdfs-default.xml/rename as dfs.name.xxx
was (Author: jojochuang):
Unrelated.
It's unfortunate the configuration is listed in core-default.xml and named as
fs.protected.directories.
It should have been named as dfs.name.xxxx, since it's only valid for HDFS.
> The feature of protect directories should be used in RenameOp
> -------------------------------------------------------------
>
> Key: HDFS-14802
> URL: https://issues.apache.org/jira/browse/HDFS-14802
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.0.4, 3.3.0, 3.2.1, 3.1.3
> Reporter: Fei Hui
> Assignee: Fei Hui
> Priority: Major
> Attachments: HDFS-14802.001.patch, HDFS-14802.002.patch,
> HDFS-14802.003.patch, HDFS-14802.004.patch
>
>
> Now we could set fs.protected.directories to prevent users from deleting
> important directories. But users can delete directories around the limitation.
> 1. Rename the directories and delete them.
> 2. move the directories to trash and namenode will delete them.
> So I think we should use the feature of protected directories in RenameOp
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
