Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <17591806.1159486071773.JavaMail.jira@brutus>
Date: Thu, 28 Sep 2006 16:27:51 -0700 (PDT)
From: "Wendy Chien (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-423) file paths are not normalized
In-Reply-To: <13847288.1154636773936.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-423?page=comments#action_12438585 ] 
            
Wendy Chien commented on HADOOP-423:
------------------------------------

You're right, I've changed the logic in the namenode check.

I don't understand where you don't want to call Path.toString(), in DFSClient?  The namenode only gets a String, which I parse for the offending sequences.    Do you mean we should convert it to a Path there?

> file paths are not normalized
> -----------------------------
>
>                 Key: HADOOP-423
>                 URL: http://issues.apache.org/jira/browse/HADOOP-423
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.4.0
>            Reporter: Christian Kunz
>         Assigned To: Wendy Chien
>             Fix For: 0.7.0
>
>         Attachments: pathnorm2.patch
>
>
> Paths containing  '.' or '..' are not normalized -- the corresponding directories actually seem to be created. This is inconsistent and unexpected behavior, and  is particularly painful when running from a working directory, using relative paths that start with ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira