[
https://issues.apache.org/jira/browse/HADOOP-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067253#comment-13067253
]
Usman Masood commented on HADOOP-7460:
--------------------------------------
The problem is that the constructor of Configured calls setConf(...) which I've
overridden in Trash so that it invokes setConf(...) for trashPolicy as well.
But this leads to the bug that FindBug highlights. I think this error will
occur as long as a constructor calls an overridden method. But it doesn't make
sense for us to setConf(...) of Trash and not change it for the underlying
TrashPolicy. Any ideas how to work around it?
We don't really have another TrashPolicy, should I just set the conf variable
fs.trash.classname to TrashPolicyDefault and see if that works as well?
> 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
