Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1381222840.1237740470810.JavaMail.jira@brutus>
Date: Sun, 22 Mar 2009 09:47:50 -0700 (PDT)
From: "Brian Bockelman (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Created: (HADOOP-5551) Namenode permits directory
 destruction on overwrite
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Namenode permits directory destruction on overwrite
---------------------------------------------------

                 Key: HADOOP-5551
                 URL: https://issues.apache.org/jira/browse/HADOOP-5551
             Project: Hadoop Core
          Issue Type: Bug
    Affects Versions: 0.19.1
            Reporter: Brian Bockelman
            Priority: Critical


The FSNamesystem's startFileInternal allows overwriting of directories.  That is, if you have a directory named /foo/bar and you try to write a file named /foo/bar, the file is written and the directory disappears.

This is most apparent for folks using libhdfs directly, as overwriting is always turned on.  Therefore, if libhdfs applications do not check the existence of a directory first, then they will permit new files to destroy directories.

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