Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 93609 invoked from network); 17 Feb 2011 21:25:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2011 21:25:50 -0000 Received: (qmail 88722 invoked by uid 500); 17 Feb 2011 21:25:49 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 88629 invoked by uid 500); 17 Feb 2011 21:25:48 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 88621 invoked by uid 99); 17 Feb 2011 21:25:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 21:25:48 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of awittenauer@linkedin.com designates 69.28.149.25 as permitted sender) Received: from [69.28.149.25] (HELO esv4-mav03.corp.linkedin.com) (69.28.149.25) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 21:25:42 +0000 DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns; h=X-IronPort-AV:Received:From:To:Subject:Thread-Topic: Thread-Index:Date:Message-ID:References:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=h1LDvivOuWFlbJt/pY1xpplV5AlShp5891johTnMriVwNCbxNVfMlD4l TPOf1lDJ4J8GroSAE+4pPgeblQqpxLgSVJ2Vs67PnQxOoL4/Zw11lfOAN KKOanOmKWvJJd1+; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=awittenauer@linkedin.com; q=dns/txt; s=proddkim; t=1297977939; x=1329513939; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Allen=20Wittenauer=20 |Subject:=20Re:=20[VOTE]=20Abandon=20hdfsproxy=20HDFS=20c ontrib|Date:=20Thu,=2017=20Feb=202011=2021:26:54=20+0000 |Message-ID:=20<71308072-C3D4-4A90-A4E7-588C91C5D088@link edin.com>|To:=20""=20|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<504A3A45A83EF14083C24E6167EF9191@linkedin .com>|In-Reply-To:=20|References:=20=0D=0A=20=0D=0A=20 <823262F0-EE37-4A0A-8F8C-D9422541D67B@mac.com>=0D=0A=20<0 CBAFDBB-AC2A-495D-8936-4DF4D6731B69@Holsman.NET>=0D=0A=20 =0D =0A=20; bh=XD5zD7I3Vb3vcr7goloisqsVXb64wJFMqKBDYO3nPOY=; b=aB+gdM4ND1LgLD22wxEcFTkLGBhG6VHZ670spVWpMMlO5pOvnUDnq9h9 1y6Hr9lTwgpYvNTOu/nMZfrkXgKpHauzsyWeeAKsGT51cZanBAt7slc7g DMMSbkGftboBAOm; X-IronPort-AV: E=Sophos;i="4.62,182,1297065600"; d="scan'208";a="20287068" Received: from ESV4-EXC01.linkedin.biz ([fe80::d7c:dc04:aea1:97d7]) by esv4-cas02.linkedin.biz ([172.18.46.142]) with mapi id 14.01.0251.000; Thu, 17 Feb 2011 13:26:54 -0800 From: Allen Wittenauer To: "" Subject: Re: [VOTE] Abandon hdfsproxy HDFS contrib Thread-Topic: [VOTE] Abandon hdfsproxy HDFS contrib Thread-Index: AQHLyZ27ICuajETxE02yFg9O1wZLWpP8Sq4AgAANWQCAAAYpgIAJS9iAgAEaQoCAAADyAA== Date: Thu, 17 Feb 2011 21:26:54 +0000 Message-ID: <71308072-C3D4-4A90-A4E7-588C91C5D088@linkedin.com> References: <823262F0-EE37-4A0A-8F8C-D9422541D67B@mac.com> <0CBAFDBB-AC2A-495D-8936-4DF4D6731B69@Holsman.NET>

In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.46.247] Content-Type: text/plain; charset="us-ascii" Content-ID: <504A3A45A83EF14083C24E6167EF9191@linkedin.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org On Feb 17, 2011, at 1:21 PM, Konstantin Shvachko wrote: > hdfsproxy is a wrapper around hftpFileSystem (in its current state). > So you can always replace hdfsproxy with hftpFileSystem. > Also it uses pure FileSystem api, so it can successfully be maintained > outside of hdfs. >=20 > Therefore I am +1 removing it from hdfs/contrib. >=20 > What is the use case for hdfsproxy anyways? A stable, secure http get interface for files. (No, the normal web ui is = not good enough. Think firewalls.).