Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8EAB10407 for ; Mon, 9 Feb 2015 23:00:45 +0000 (UTC) Received: (qmail 34159 invoked by uid 500); 9 Feb 2015 23:00:45 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 34060 invoked by uid 500); 9 Feb 2015 23:00:45 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 34048 invoked by uid 99); 9 Feb 2015 23:00:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 23:00:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rhshriva@gmail.com designates 209.85.214.173 as permitted sender) Received: from [209.85.214.173] (HELO mail-ob0-f173.google.com) (209.85.214.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 23:00:20 +0000 Received: by mail-ob0-f173.google.com with SMTP id uy5so28520045obc.4 for ; Mon, 09 Feb 2015 14:58:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=663u8GtX1eC8xY9vEcdWghXP/gHvU+RuWHaOUc0iC58=; b=SiRKgtXM+vQb0nyNaj0pcZ+dLXy8jrN4XtE/04e5u9fJxdZjfXMNzEdYZ/+QYYSyxr KhOzUSltfVEfMQQyYW1dIIvBdHRsVSmMekLdLYQmDYu8yh1GSHvCkA6VW1Ah5Ckx/ino IIx4wy+of438brqwymyUvUaCgd8eV31Jb5EGpH1i8D1UNjtivHyJ7qdYxLtFScUo0D7r JYwewXf8WC3w7/IhIrROC9onlTPFCOkLAc7JV0v/NlnUKuP6K16jUdg1oyL4NVRAGzU8 4V0duBIQ/gUoA2Xv7z/uDyM6vr672L6BCSKOiUGmgn8RKndJDG1KHruUwK8k1FGfOP6k a6xg== MIME-Version: 1.0 X-Received: by 10.60.141.41 with SMTP id rl9mr13496803oeb.31.1423522683331; Mon, 09 Feb 2015 14:58:03 -0800 (PST) Received: by 10.202.91.133 with HTTP; Mon, 9 Feb 2015 14:58:03 -0800 (PST) In-Reply-To: <1023034372.1349736.1423522397407.JavaMail.yahoo@mail.yahoo.com> References: <1023034372.1349736.1423522397407.JavaMail.yahoo@mail.yahoo.com> Date: Mon, 9 Feb 2015 14:58:03 -0800 Message-ID: Subject: Re: Proxy for HDFS From: Rahul Shrivastava To: hdfs-dev@hadoop.apache.org, Rajiv Chittajallu Content-Type: multipart/alternative; boundary=047d7b3a8e92deaa0b050eafb38e X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a8e92deaa0b050eafb38e Content-Type: text/plain; charset=UTF-8 Thanks Rajiv. I did look into HttpFs before but i wanted a build a proxy at HDFS layer. This is specific for clients which do not use HTTP ( i.e. HttpFs or webHDFS) to talk to the HDFS cluster. That includes clients which uses HDFS driver to talk to HDFS cluster. thanks Rahul On Mon, Feb 9, 2015 at 2:53 PM, Rajiv Chittajallu < rajive@yahoo-inc.com.invalid> wrote: > > https://github.com/apache/hadoop/tree/branch-2.6/hadoop-hdfs-project/hadoop-hdfs-httpfs > > > > > ----- Original Message ----- > From: Rahul Shrivastava > To: hdfs-dev@hadoop.apache.org > Cc: > Sent: Monday, February 9, 2015 2:35 PM > Subject: Proxy for HDFS > > Hi, > > I have looking in HDFS code base ( 2.6.0) for the last couple of days for > any possible proxy that we could utilize to create a proxy for HDFS. > Is there any hook within HDFS to build a proxy around that. > > thanks > Rahul > --047d7b3a8e92deaa0b050eafb38e--