Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 28842 invoked from network); 12 Aug 2009 11:58:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Aug 2009 11:58:41 -0000 Received: (qmail 9287 invoked by uid 500); 12 Aug 2009 11:58:47 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 9231 invoked by uid 500); 12 Aug 2009 11:58:46 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 9221 invoked by uid 99); 12 Aug 2009 11:58:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2009 11:58:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.85.219.226] (HELO mail-ew0-f226.google.com) (209.85.219.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2009 11:58:34 +0000 Received: by ewy26 with SMTP id 26so4500782ewy.29 for ; Wed, 12 Aug 2009 04:58:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.88.14 with SMTP id z14mr7745wee.25.1250078293968; Wed, 12 Aug 2009 04:58:13 -0700 (PDT) In-Reply-To: <4A819893.6070509@yahoo-inc.com> References: <45f85f70908101335s547cf264t47489e66a47cbbff@mail.gmail.com> <1267dd3b0908101637m7acc6e76u5116c9970d47447a@mail.gmail.com> <4A818F00.3090401@apache.org> <4A819893.6070509@yahoo-inc.com> Date: Wed, 12 Aug 2009 12:58:13 +0100 Message-ID: Subject: Re: Contributing a New FileSystem Implementation - Questions About Process From: Tom White To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 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 wrot= e: > Jonathan, > > in case you need to take a look at a common testplan template you can fin= d > 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 =A0and not contrib, so thanks for the clarificati= on. >>> >> >> what's the test plan going to be for a new FS? >