[
https://issues.apache.org/jira/browse/HDFS-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065146#comment-13065146
]
Uma Maheswara Rao G commented on HDFS-2128:
-------------------------------------------
Can we have some kind of TrashFactory, which will create the instance of Trash
policy implementaions.Bydefault it can create Trash.java instance. Trash.java
class will not be changed and deprecate the constructor. If we configure some
class for Trash policy(fs.trash.classname), then factory Should create that
instance. We can define one Base interface for Trash policies and in Future let
all Trash policy implemantations implement those APIs(looks you already
identified the APIs) from Base trash interface.
In Future only TrashFactory will be used to get the Trash instance.
As Doug said, Presntly let dont distrurb the Trash class. So that no existing
users will get effected.
Also, Currently Trash implementaions present in Common, So can we move this
issue to common?
> Support for pluggable Trash policies
> ------------------------------------
>
> Key: HDFS-2128
> URL: https://issues.apache.org/jira/browse/HDFS-2128
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Reporter: dhruba borthakur
> Assignee: Usman Masood
> Attachments: PluggableTrash.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
