[
https://issues.apache.org/jira/browse/HADOOP-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065659#comment-13065659
]
Usman Masood commented on HADOOP-7460:
--------------------------------------
Oh, I think I didn't get you the last time. Yeah I think adding a layer of
indirection should definitely make this cleaner. We can rename checkpoint() and
expunge() to create/deleteSnapshot() in TrashPolicy this way as well.
Though I'm just wondering if there are some clients which make some assumptions
based on the implementation of Trash when they use it? This might break things
for them.
> 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
