Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 25 Aug 2011 23:20:29 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <3644040.15541.1314314429667.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=13091409#comment-13091409 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-2284:
----------------------------------------------

The idea is to have a full feature hdfs http interface.  Hftp does not support write and SPNEGO.  Hoop does not have random redirection and does not preserve data locality.  It seems that it does not have support/native support of position read, iterative ls, file checksum, get/renew/cancel delegation token and file concat.  We are going to combine the features in hftp and hoop.  Since it is an incompatible change if we change hftp://, it is better to have a new scheme, say httpfs://.  (Any suggestion of the scheme name?)  httpfs is a replacement of hftp but not hoop since it would not have a proxy server.

> 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