[
https://issues.apache.org/jira/browse/HADOOP-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068198#comment-13068198
]
Usman Masood commented on HADOOP-7460:
--------------------------------------
I know what the issue is, I was asking for ideas for a solution. The problem is
if someone calls setConf(...) on Trash post construction, then it should also
change the conf for TrashPolicy, no? If this isn't needed, then I can just
remove the overridden setConf(...) in Trash and the issue will be resolved.
> 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,
> PluggableTrash_V3.patch, PluggableTrash_V4.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