[
https://issues.apache.org/jira/browse/HDFS-15243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083986#comment-17083986
]
Ayush Saxena commented on HDFS-15243:
-------------------------------------
If I remember correct, there was a discussion that {{ fs.protected.directories
}} this should not be in Hadoop-Common since this HDFS specific, but couldn't
move to HDFS due to compatibility issues.
Since now we are introducing a new configuration, which already we know is only
HDFS specific, there is no point putting it in Common, the object stores and
other fs won't respect that.
I don't think there would be any problem, if this is kept in HDFS, we can
properly document it, so it doesn't get unnoticed.
> 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: [email protected]
For additional commands, e-mail: [email protected]
