[
https://issues.apache.org/jira/browse/HADOOP-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HADOOP-8710:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0-alpha
Target Version/s: (was: 2.2.0-alpha)
Release Note: The trash emptier may no longer be run using {{hadoop
org.apache.hadoop.fs.Trash}}. The trash emptier runs on the NameNode (if
configured). Old trash checkpoints may be deleted using {{hadoop fs -expunge}}.
Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change)
Status: Resolved (was: Patch Available)
Thanks for the review ATM. I've committed this and merged to branch-2.
> Remove ability for users to easily run the trash emptier
> --------------------------------------------------------
>
> Key: HADOOP-8710
> URL: https://issues.apache.org/jira/browse/HADOOP-8710
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 2.2.0-alpha
>
> Attachments: hadoop-8710.txt
>
>
> Users can currently run the emptier via {{hadoop
> org.apache.hadoop.fs.Trash}}, which seems error prone as there's nothing in
> that command that suggests it runs the emptier and nothing that asks you
> before deleting the trash for all users (that the current user is capable of
> deleting). Given that the trash emptier runs server side (eg on the NN) let's
> remove the ability to easily run it client side. Marking as an incompatible
> change since someone expecting the hadoop command with this class specified
> to empty trash will no longer be able to (they'll need to create their own
> class that does this).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
