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

Andras Bokor commented on HADOOP-7363:
--------------------------------------

[^HADOOP-7363.01.patch] was tested on Windows, CentOS and Mac.
Notes:
# I consider Windows and Mac as non-case sensitive filesystem. So related tests 
will skipped.
# I set rename support to false to skip the related tests. See HADOOP-13082 for 
details.
# I overwrote {{path}} method. A lot of tests are based on writing root 
directory which is not permitted on local filesystems. Instead the tests will 
work into target directory.
# {{testLSRootDir}} and {{testListStatusRootDir}} will also work into target 
instead of root directory. It tries to create a directory on root which is not 
allowed to test user. With this solution we are still able to test the listing 
and status checking functions of the filesystem. I did not see any reason to 
force the code to work on root. In case of a raw local fs there is no 
difference between / and other directories (other than permissions). 
# Please help whether I chose correct package for my new test.

In spite of that it fails until HADOOP-13073 resolved/merged a review is 
welcome.

> TestRawLocalFileSystemContract is needed
> ----------------------------------------
>
>                 Key: HADOOP-7363
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7363
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: fs
>    Affects Versions: 0.23.0
>            Reporter: Matt Foley
>            Assignee: Matt Foley
>         Attachments: HADOOP-7363.01.patch
>
>
> FileSystemContractBaseTest is supposed to be run with each concrete 
> FileSystem implementation to insure adherence to the "contract" for 
> FileSystem behavior.  However, currently only HDFS and S3 do so.  
> RawLocalFileSystem, at least, needs to be added. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to