hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7460) Support for pluggable Trash policies
Date Mon, 18 Jul 2011 20:49:57 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067289#comment-13067289
] 

Suresh Srinivas commented on HADOOP-7460:
-----------------------------------------

> I think fs, trash can be moved up to TrashPolicy. Not sure about current, homesParent,
deletionInterval though. Some TrashPolicy might not require these vars?

They can ignore it then right?

> but thinking about it more I don't really see any reason why TrashPolicy should only
be accessible via Trash
That was not the reason why I was thinking about making it public. If new trash policy can
be implemented by users, then it should be a public API.

> 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

        

Mime
View raw message