Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D61B19543 for ; Fri, 1 Jun 2012 21:37:24 +0000 (UTC) Received: (qmail 22292 invoked by uid 500); 1 Jun 2012 21:37:24 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 22228 invoked by uid 500); 1 Jun 2012 21:37:24 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 22027 invoked by uid 99); 1 Jun 2012 21:37:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2012 21:37:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id E78B0141663 for ; Fri, 1 Jun 2012 21:37:23 +0000 (UTC) Date: Fri, 1 Jun 2012 21:37:23 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1657720440.28446.1338586643950.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1871149209.13350.1337334010403.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8409) Address Hadoop path related issues on Windows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287693#comment-13287693 ] Daryn Sharp commented on HADOOP-8409: ------------------------------------- To further clarify, nothing else that uses a {{Path}} is prepared to handle fragments, so the fragment will be silently munched off the uri. In the prior example, the path effectively becomes "." which is the cwd. Trying to remove a qualified path such as "some/path/#1" would remove the parent directory. I think it's prudent to not spread the DC's semantics of fragments throughout hadoop when nothing else is prepared to deal with fragments. > Address Hadoop path related issues on Windows > --------------------------------------------- > > Key: HADOOP-8409 > URL: https://issues.apache.org/jira/browse/HADOOP-8409 > Project: Hadoop Common > Issue Type: Bug > Components: fs, test, util > Affects Versions: 1.0.0 > Reporter: Ivan Mitic > Assignee: Ivan Mitic > Attachments: HADOOP-8409-branch-1-win.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > There are multiple places in prod and test code where Windows paths are not handled properly. From a high level this could be summarized with: > 1. Windows paths are not necessarily valid DFS paths (while Unix paths are) > 2. Windows paths are not necessarily valid URIs (while Unix paths are) > #1 causes a number of tests to fail because they implicitly assume that local paths are valid DFS paths (by extracting the DFS test path from for example "test.build.data" property) > #2 causes issues when URIs are directly created on path strings passed in by the user -- 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