Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <839890967.1212221986503.JavaMail.jira@brutus>
Date: Sat, 31 May 2008 01:19:46 -0700 (PDT)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3474) Need an option -rm and -rmr to
 *not* move to Trash, but actually delete
In-Reply-To: <1697818200.1212186285100.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Owen O'Malley commented on HADOOP-3474:
---------------------------------------

In such situations, I use:

{code}
hadoop fs -rmr foo bar .Trash
{code}

> Need an option -rm and -rmr to *not* move to Trash, but actually delete
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-3474
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3474
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: fs
>    Affects Versions: 0.17.0
>            Reporter: Milind Bhandarkar
>
> By default, when Trash is enabled, -rm and -rmr just move files/directories to .Trash, which are actually deleted after some time set in the config.
> When DFS gets full, we need to quickly create space on it by deleting files, so it will be good to have a --force option to both -rm and -rmr, so that files are actually deleted and not moved.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.