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

Steve Loughran commented on HADOOP-9355:
----------------------------------------

I've been working on better testing on HADOOP-9258; and have factored out a 
large set of tests for each method in {{FileSystem}}, currently out of svn in 
[github|https://github.com/hortonworks/Hadoop-and-Swift-integration/tree/master/swift-file-system/src/test/java/org/apache/hadoop/fs/swift]
 

I've been thinking about how best to pull these into trunk in a way that makes 
it possible for FS implementation classes to be more declarative about what 
they support (append, permissions, immediate-consistency, atomic-rename, 
atomic-delete, etc) -which would be done by providing a properties file 
describing the features.

# I like the wrapper making tests available to both {{FileSystem}} and 
{{FileContext}}.
# I think we should think about moving FS contract tests to their own package, 
as .fs is too bloated; something like {{fs.contract}}.
# I'd like to see these symlink tests as part of a bigger rework of the FS 
tests -one in which we could get the initial design in with these and some of 
the SwiftFS tests -and slowly evolve to tighten down the interfaces' 
specifications

I'll open a JIRA on it, and we could split out the abstract FS bindings here 
from the symlinks, which would be just one of the methods to be tested more 
rigorously.

What do you think?

                
> Abstract symlink tests to use either FileContext or FileSystem
> --------------------------------------------------------------
>
>                 Key: HADOOP-9355
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9355
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: hadoop-9355-wip.patch
>
>
> We'd like to run the symlink tests using both FileContext and the upcoming 
> FileSystem implementation. The first step here is abstracting the test logic 
> to run on an abstract filesystem implementation.

--
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

Reply via email to