Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 95939 invoked from network); 12 Feb 2008 07:20:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2008 07:20:41 -0000 Received: (qmail 13636 invoked by uid 500); 12 Feb 2008 07:20:28 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 13601 invoked by uid 500); 12 Feb 2008 07:20:28 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 13592 invoked by uid 99); 12 Feb 2008 07:20:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2008 23:20:28 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fullung@gmail.com designates 72.14.246.251 as permitted sender) Received: from [72.14.246.251] (HELO ag-out-0708.google.com) (72.14.246.251) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 07:19:57 +0000 Received: by ag-out-0708.google.com with SMTP id 23so11961643agd.5 for ; Mon, 11 Feb 2008 23:20:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=1AQLOjHmrdvEwhTlgHo9ww51UWTZinVaRSyMaeytBmc=; b=nRiMPNkGfMOIlzomcExJ+dAY3j5lnNXlEbKIJ/Sw18gSO6gVWhFZyH6SCkPFWYWpVwVdCrArWw08VfDoScAwmpnEK3SkB4vSRBdL0ztFxHuXBZb6hI4zP4MK7JdkmKSbbganDkRPrQZ5xnqCgpAXNQKP+Q6b/rkr2t5VsmCjbFg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X8UIcZHbTNDJeU4Je469Zb5dvfU5ZkWRa4dTa4lZqgCNlWc1KeanpxM8NOIraAjvrp8zAdWpfD6U2AqDiF93e8GoIHqfhhWkg1OWLHEC5VMqTtevgfxHVo1RFNhlU9+3+vX+svPA9Zmgq79T9F2/X5w9Ltlt0ih1OevE/lUykgE= Received: by 10.142.126.17 with SMTP id y17mr728543wfc.170.1202800802980; Mon, 11 Feb 2008 23:20:02 -0800 (PST) Received: by 10.142.213.16 with HTTP; Mon, 11 Feb 2008 23:20:02 -0800 (PST) Message-ID: <5eec5f300802112320w65ed8d8cm91601c3fba3a917a@mail.gmail.com> Date: Tue, 12 Feb 2008 09:20:02 +0200 From: "Albert Strasheim" To: core-user@hadoop.apache.org Subject: Re: Using Hadoop as a shared file system In-Reply-To: <47B0CFDA.1050308@alum.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <006101c86cfb$316ce3b0$c884e892@sun.ac.za> <47B0CFDA.1050308@alum.mit.edu> X-Virus-Checked: Checked by ClamAV on apache.org Hello, I'm not exactly sure how to apply WebDAV to the scenario I outlined. As I said, I would like to avoid having to duplicate my data inside a HDFS. Once I have that, I guess I could expose it as a WebDAV service when HADOOP-496 gets done. If you mean a WebDAV setup outside of Hadoop, that is something I could possibly consider, but I would like to reuse the Hadoop FileSystem interface if possible. I'd prefer not to have to integrate a WebDAV server and client into my Java code if I can just reuse work from Hadoop. Comments? Regards, Albert On Feb 12, 2008 12:44 AM, Fernando Padilla wrote: > Have you put any thought into Webdav? Or did you write that off as well?