Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 92021 invoked from network); 3 Aug 2007 00:18:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Aug 2007 00:18:16 -0000 Received: (qmail 74053 invoked by uid 500); 3 Aug 2007 00:18:15 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 74024 invoked by uid 500); 3 Aug 2007 00:18:15 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 74012 invoked by uid 99); 3 Aug 2007 00:18:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2007 17:18:15 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2007 00:17:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1EF187141F5 for ; Thu, 2 Aug 2007 17:17:53 -0700 (PDT) Message-ID: <19371760.1186100273124.JavaMail.jira@brutus> Date: Thu, 2 Aug 2007 17:17:53 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-1665) DFS Trash feature bugs In-Reply-To: <16797562.1185836032824.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1665: ------------------------------------- Attachment: Trash.patch If the file already exists in Trash, then append an integer to the filename in the Trash directory. The newer versions of the file in Trash will be of the form path.0, path.1, path.2, etc. > DFS Trash feature bugs > ---------------------- > > Key: HADOOP-1665 > URL: https://issues.apache.org/jira/browse/HADOOP-1665 > Project: Hadoop > Issue Type: Bug > Components: dfs > Affects Versions: 0.13.1 > Reporter: Nigel Daley > Assignee: Doug Cutting > Priority: Blocker > Fix For: 0.14.0 > > Attachments: Trash.patch > > > In testing the DFS Trash feature, I've run across a couple of bugs. > 1) Attempting to remove the same file fails when attempted within the same fs.trash.interval: > % bin/hadoop dfs -put file /file > % bin/hadoop dfs -rm /file > Moved to trash: /file > % bin/hadoop dfs -put file /file > % bin/hadoop dfs -rm /file > rm: Failed to move to trash: /file > 2) Removing a file within a directory, followed by removing the directory creates a bizzare hierarchy within /Trash: > % bin/hadoop dfs -mkdir /dir > % bin/hadoop dfs -put file /dir/file > % bin/hadoop dfs -rm /dir/file > Moved to trash: /dir/file > % bin/hadoop dfs -rmr /dir > Moved to trash: /dir > % bin/hadoop dfs -lsr /Trash > /Trash/Current > /Trash/Current/dir > /Trash/Current/dir/dir <-- This is weird; potentially related to a rename case not fixed by HADOOP-1623 ??? > /Trash/Current/dir/file 10 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.