[
https://issues.apache.org/jira/browse/HDFS-16977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714150#comment-17714150
]
ASF GitHub Bot commented on HDFS-16977:
---------------------------------------
ayushtkn commented on PR #5547:
URL: https://github.com/apache/hadoop/pull/5547#issuecomment-1514909124
Accidental deletes are protected via Trash, if someone deletes something
accidentally, he can recover from Trash. Having such configurations seems
overkill for this situation.
FsShell is not centric just to HDFS, it can be used by other FileSystems
also. Doesn't makes sense to me for this use case
> Forbid assigned characters in pathname.
> ---------------------------------------
>
> Key: HDFS-16977
> URL: https://issues.apache.org/jira/browse/HDFS-16977
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: dfsclient, namenode
> Affects Versions: 3.3.4
> Reporter: WangYuanben
> Priority: Minor
> Labels: pull-request-available
>
> Some pathnames which contains special character(s) may lead to unexpected
> results. For example, there is a file named "/foo/file*" in my cluster,
> created by "DistributedFileSystem.create(new Path("/foo/file*"))". When I
> want to remove it, I type in "hadoop fs -rm /foo/file*" in shell. However, I
> remove all the files with the prefix of "/foo/file*" unexpectedly. There are
> also some other characters just like '*', such as ' ', '|', '&', etc.
>
> Therefore, it's necessary to restrict the occurrence of these characters in
> pathname. A simple but effective way is to forbid assigned characters in
> pathname when new file or directory is created.
>
> It is also important to add the same function on the Router model and WebHdfs
> model. I will add them as two subtasks later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
