Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 6 Dec 2011 16:51:40 +0000 (UTC)
From: "Eli Collins (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <953191744.46087.1323190300503.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <208483421.9470.1311196562996.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2178) Contributing Hoop to HDFS,
 replacement for HDFS proxy with read/write capabilities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins commented on HDFS-2178:
-----------------------------------

bq. Technically we could move Hoop under common. But Hoop depends on HDFS for testing which it may be seen as a circular dependency (i'm saying may because in practice it is not, but module dir organization would suggest that).

If it's not hdfs-specific then common is the right place. We have the same issue with other non-hdfs-specific features that live in common (eg the client side mount table and symlinks). In terms of test structure you can make TestHttpFSFileSystem a base class and have TestHDFSBasedHttpFileSystem and TestWebhdfsBasedFileSystem live in HDFS. Make sense? 
                
> Contributing Hoop to HDFS, replacement for HDFS proxy with read/write capabilities
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-2178
>                 URL: https://issues.apache.org/jira/browse/HDFS-2178
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.23.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.24.0, 0.23.1
>
>         Attachments: HDFS-2178.patch, HDFS-2178.patch, HDFS-2178.patch, HDFS-2178.patch, HDFS-2178.patch, HDFS-2178.patch, HDFS-2178.patch, HDFSoverHTTP-API.html, HdfsHttpAPI.pdf
>
>
> We'd like to contribute Hoop to Hadoop HDFS as a replacement (an improvement) for HDFS Proxy.
> Hoop provides access to all Hadoop Distributed File System (HDFS) operations (read and write) over HTTP/S.
> The Hoop server component is a REST HTTP gateway to HDFS supporting all file system operations. It can be accessed using standard HTTP tools (i.e. curl and wget), HTTP libraries from different programing languages (i.e. Perl, Java Script) as well as using the Hoop client. The Hoop server component is a standard Java web-application and it has been implemented using Jersey (JAX-RS).
> The Hoop client component is an implementation of Hadoop FileSystem client that allows using the familiar Hadoop filesystem API to access HDFS data through a Hoop server.
>   Repo: https://github.com/cloudera/hoop
>   Docs: http://cloudera.github.com/hoop
>   Blog: http://www.cloudera.com/blog/2011/07/hoop-hadoop-hdfs-over-http/
> Hoop is a Maven based project that depends on Hadoop HDFS and Alfredo (for Kerberos HTTP SPNEGO authentication). 
> To make the integration easy, HDFS Mavenization (HDFS-2096) would have to be done first, as well as the Alfredo contribution (HADOOP-7119).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira