hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Seidman <jonathan.seid...@opendatagroup.com>
Subject Re: Contributing a New FileSystem Implementation - Questions About Process
Date Wed, 12 Aug 2009 21:38:27 GMT
Thanks for the pointers Tom and Cos, this is helpful. We'll take a look at
these as we firm up our test plan.

On Wed, Aug 12, 2009 at 6:58 AM, Tom White <tom@cloudera.com> wrote:

> Hi Jonathan,
>
> For testing you can subclass FileSystemContractBaseTest and create an
> instance of the filesystem to test in the set up method, to check that
> the new implementation conforms to the contract of the FileSystem
> interface (although see also
> https://issues.apache.org/jira/browse/HDFS-303).
>
> See TestHDFSFileSystemContract for an example.
>
> Cheers,
> Tom
>
> On Tue, Aug 11, 2009 at 5:13 PM, Konstantin Boudnik<cos@yahoo-inc.com>
> wrote:
> > Jonathan,
> >
> > in case you need to take a look at a common testplan template you can
> find
> > one in HDFS-265 or more generic in HADOOP-5587
> >
> > Cos
> >
> > On 8/11/09 8:32 AM, Steve Loughran wrote:
> >>
> >> Jonathan Seidman wrote:
> >>>
> >>> Thanks for the replies. We'll create a patch for trunk and then include
> a
> >>> 0.18 compatible patch with the Jira, as you suggest.
> >>>
> >>> Based on other contributed FileSystem implementations, we were assuming
> >>> this
> >>> should go in o.a.h.fs  and not contrib, so thanks for the
> clarification.
> >>>
> >>
> >> what's the test plan going to be for a new FS?
> >
>



-- 
Jonathan Seidman
Open Data Group

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message