[
https://issues.apache.org/jira/browse/HADOOP-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852098#comment-16852098
]
Ahmed Hussein commented on HADOOP-7310:
---------------------------------------
+1 to solution A
I suggest to modify the {{DistributedFileSystem}} trash implementation to do
the following:
# Add a configuration option that represents a list of trash directories
"{{TrashRoots"}}.
# Each time a file gets deleted, the trash is located by looping on the
TrashRoots and returning the first existing directory. If no such directory
exists, the system defaults to the old policy (i.e, {{./user/user1/.Trash}})
# In order to be backward compatible, the {{TrashPolicy.Emptier}} looks in two
different locations: the {{TrashRoots}} and to the default user trash folders (
i.e, {{./user/user1/.Trash}}).
# Since EZ already put trash at the top of respective zone, the EZ won't be
modified.
*Requirements*:
# Define a comma separated list of trash directories in the config file.
# Admins create trash directories. If all the {{TrashRoots}} directories are
missing, the deleted files will be moved to user trash directories.
This approach does not change the FS API and endures minimum changes to the
code.
> Trash location needs to be revisited
> ------------------------------------
>
> Key: HADOOP-7310
> URL: https://issues.apache.org/jira/browse/HADOOP-7310
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.0.0-alpha
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
