[
https://issues.apache.org/jira/browse/HADOOP-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065652#comment-13065652
]
Suresh Srinivas commented on HADOOP-7460:
-----------------------------------------
> To preserve backward compatibility, I chose not to rename Trash to something
> like TrashPolicyDefault or something. If Trash uses/contains TrashPolicy then
> it doesn't make sense to have an implementation in it. I think it's best to
> separate implementation of a Trash policy from what the policy actually is.
> This is similar to how BlockPacementPolicy has been set up.
I am not sure what you mean by this.
All I am suggesting is, use Trash as Facade. It reference TrashPolicy (base
class) and points to the implementation of the TrashPolicy which provide
specialization. Some what along the lines of ->
http://en.wikipedia.org/wiki/Strategy_pattern.
> Support for pluggable Trash policies
> ------------------------------------
>
> Key: HADOOP-7460
> URL: https://issues.apache.org/jira/browse/HADOOP-7460
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Reporter: dhruba borthakur
> Assignee: Usman Masood
> Attachments: PluggableTrash.patch, PluggableTrash_V2.patch
>
>
> It would be beneficial to make the Trash policy pluggable. One primary
> use-case for this is to archive files (in some remote store) when they get
> removed by Trash emptier.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
