Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 29 Aug 2011 18:52:37 +0000 (UTC)
From: "Milind Bhandarkar (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1039788804.4302.1314643957808.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1620686924.10654.1314217949077.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2284) RW Http access to HDFS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093080#comment-13093080 ] 

Milind Bhandarkar commented on HDFS-2284:
-----------------------------------------

@Alejandro, as I have said before, having Hoop as http-based HDFS proxy, layered on top of the FileSystem API, and implementing Filesystem APIs as a wrapper on top of hoop makes complete sense to me (indeed, that was what hdfs proxy v3, abandoned last year (?), was supposed to do.) What I am concerned about, is: *two different implementations of the same APIs inside the hdfs daemons*. According to Sanjay, the reasoning for this second implementation is lack of wire compatibility in native RPC. My assumption, based on the recent activity in hdfs-dev, is that wire-compatibility in HDFS native RPC is coming soon (i.e. within next year). Therefore, I am seeking answers about the *real* use case of embedding hoop inside NN/DN.

Keeping Hoop as a layer on top of FS APIs enables a hadoop-client-free data import-export mechanism across *all* the file systems that have FS binding for Hadoop.

> RW Http access to HDFS
> ----------------------
>
>                 Key: HDFS-2284
>                 URL: https://issues.apache.org/jira/browse/HDFS-2284
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Sanjay Radia
>            Assignee: Tsz Wo (Nicholas), SZE
>
> HFTP allows on read access to HDFS via HTTP. Add RW HTTP access to HDFS)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira