Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 22 Aug 2013 08:35:51 +0000 (UTC)
From: "Binglin Chang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12664945.1377129311205.15955.1377160551958@arcas>
In-Reply-To: <JIRA.12664945.1377129311205@arcas>
References: <JIRA.12664945.1377129311205@arcas>
Subject: [jira] [Commented] (HDFS-5125)
 TestCreateEditsLog#testCanLoadCreatedEditsLog fails on Windows in
 globStatus
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747364#comment-13747364 ] 

Binglin Chang commented on HDFS-5125:
-------------------------------------

Sorry, after reading more related code, it looks like the convention is: "/C:" should be relative path and "/C:/" should be absolute. 
globStatus try each component using getFileLinks status without "/" suffix, which leads to the exception thrown.

I think this behavior is really confusing in many ways:
1. if "/C:" is relative, which path is it relative to? If it is workingDir, what if working dir is at another drive? For example: "/D:/foo".
2. if "xxx/foo" is absolute, we can no longer assume "xxx" is absolute.

Is any reason or benefit of making "/X:" relative?

                
> TestCreateEditsLog#testCanLoadCreatedEditsLog fails on Windows in globStatus
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-5125
>                 URL: https://issues.apache.org/jira/browse/HDFS-5125
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0, 2.1.1-beta
>            Reporter: Chris Nauroth
>
> This test calls the {{CreateEditsLog}} tool, then runs {{globStatus}} on the local file system to find the resulting files before moving them to a directory where a NameNode can start up and read them.  The HADOOP-9877 patch has caused this test to start failing on Windows due to internal calls to {{FileContext#getFileLinkStatus}} rejecting the {{Path}} arguments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira