hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9361) Strictly define the expected behavior of filesystem APIs and write tests to verify compliance
Date Sun, 01 Jun 2014 21:37:03 GMT

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

Steve Loughran commented on HADOOP-9361:
----------------------------------------

Jay -what I'm thinking of is that functional filesystem tests written in the bigtop project
may want to make use of some of the information. What is there today is low-level, and covers
details needed for the basic filesystem tests, but what would be interesting is information
on the limits of the filesystem
# the maximum number of files in a directory
# the maximum path length in the filesystem
# the maximum length of a directory entry
# the maximum file size


these can be used for stress tests -though of course they'd need to be overrideable by individuals/test
runs. 

this is stuff that could/should be kept together with the other details. The hadoop build
keeps XML and properties resources out of the test JARs, which is normally good: it stops
log4j files sneaking it, or people's site.xml files with login details accidentally being
published. its just we may want -at some time in the future- to publish this -for testers
rather than apps in general


> Strictly define the expected behavior of filesystem APIs and write tests to verify compliance
> ---------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9361
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9361
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs, test
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-9361-001.patch, HADOOP-9361-002.patch, HADOOP-9361-003.patch,
HADOOP-9361-004.patch, HADOOP-9361-005.patch, HADOOP-9361-006.patch, HADOOP-9361-007.patch,
HADOOP-9361-008.patch, HADOOP-9361-009.patch, HADOOP-9361-011.patch, HADOOP-9361-012.patch,
HADOOP-9361-013.patch, HADOOP-9361-014.patch
>
>
> {{FileSystem}} and {{FileContract}} aren't tested rigorously enough -while HDFS gets
tested downstream, other filesystems, such as blobstore bindings, don't.
> The only tests that are common are those of {{FileSystemContractTestBase}}, which HADOOP-9258
shows is incomplete.
> I propose 
> # writing more tests which clarify expected behavior
> # testing operations in the interface being in their own JUnit4 test classes, instead
of one big test suite. 
> # Having each FS declare via a properties file what behaviors they offer, such as atomic-rename,
atomic-delete, umask, immediate-consistency -test methods can downgrade to skipped test cases
if a feature is missing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message