[
https://issues.apache.org/jira/browse/HDFS-15243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083942#comment-17083942
]
Ayush Saxena commented on HDFS-15243:
-------------------------------------
Thanx [~rain_lyy] for the patch.
Seems you have moved {{fs.protected.directories}} from common to hdfs, that
isn't required. You just have your new configuration at HDFS, moving
configuration from Common to Hdfs will create Compatibility issues.
The new configuration name should start form dfs not from fs
> Child directory should not be deleted or renamed if parent directory is a
> protected directory
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-15243
> URL: https://issues.apache.org/jira/browse/HDFS-15243
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: 3.1.1
> Affects Versions: 3.1.1
> Reporter: liuyanyu
> Assignee: liuyanyu
> Priority: Major
> Attachments: HDFS-15243.001.patch, HDFS-15243.002.patch,
> HDFS-15243.003.patch, HDFS-15243.004.patch, image-2020-03-28-09-23-31-335.png
>
>
> HDFS-8983 add fs.protected.directories to support protected directories on
> NameNode. But as I test, when set a parent directory（eg /testA) to
> protected directory, the child directory (eg /testA/testB) still can be
> deleted or renamed. When we protect a directory mainly for protecting the
> data under this directory , So I think the child directory should not be
> delete or renamed if the parent directory is a protected directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
