[
https://issues.apache.org/jira/browse/HADOOP-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556649#action_12556649
]
Hairong Kuang commented on HADOOP-2514:
---------------------------------------
> I'm confused by this. Moving something to the trash is not deleting it, it's
> moving it.
I think move-to-trash is more like a delayed deletion instead of a move. All
the files that are moved to the trash should be able to be removed later on. I
do not think it makes sense to have files be in the trashbin forever. So I
think checking for deletion permission should be performed at the trashing time.
I am not alone at this. Check http://www.ramendik.ru/docs/trashspec.html, in
which it states: " When trashing a file or directory, the implementation should
check whether the user has the necessary permissions to delete it, before
starting the trashing operation itself."
> Trash and permissions don't mix
> -------------------------------
>
> Key: HADOOP-2514
> URL: https://issues.apache.org/jira/browse/HADOOP-2514
> Project: Hadoop
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Robert Chansler
> Fix For: 0.16.0
>
>
> Shell command "rm" is really "mv" to trash with the expectation that the
> server will at some point really delete the contents of trash. With the
> advent of permissions, a user can "mv" folders that the user cannot "rm". The
> present trash feature as implemented would allow the user to suborn the
> server into deleting a folder in violation of the permissions model.
> A related issue is that if anybody can mv a folder to the trash anybody else
> can mv that same folder from the trash. This may be contrary to the
> expectations of the user.
> What is a better model for trash?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
