[ 
https://issues.apache.org/jira/browse/HADOOP-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663148#action_12663148
 ] 

Tsz Wo (Nicholas), SZE commented on HADOOP-5010:
------------------------------------------------

>.. does it make sense to do away with the artificial HFTP/HSFTP protocols, and 
>instead simply offer standard HTTP and HTTPS? 

HFTP is a file system interface, which is currently implemented with HTTP.  I 
agree if you say that the name HFTP is bad or miss-leading.

The "artificial" part of HFTP defines the way of accessing the file system.  
For example, 
{code}
Path p = new Path("hftp://namenode:port/foo/bar";);
FileStatus status = p.getFileSystem(conf).listStatus(p);
...
{code}
the code above is indeed accessing 
"http://namenode:port/listPaths/foo/bar?ugi=user,groups";, where listPaths is a 
servlet running on the NameNode and ugi is a parameter.  Then the NameNode will 
reply the output in xml format back to the HFTP client.  The HFTP client 
constructs a FileStatus object and returns it.  Without the HFTP interface, 
clients have to know all the details including the servlet name, url 
parameters, xml format, etc. in order to access the file system.

I think we cannot simply use standard HTTP because it does not support file 
system access.

> Replace HFTP/HSFTP with plain HTTP/HTTPS
> ----------------------------------------
>
>                 Key: HADOOP-5010
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5010
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/hdfsproxy
>    Affects Versions: 0.18.0
>            Reporter: Marco Nicosia
>
> In HADOOP-1563, [~cutting] wrote:
> bq. The URI for this should be something like hftp://host:port/a/b/c, since, 
> while HTTP will be used as the transport, this will not be a FileSystem for 
> arbitrary HTTP urls.
> Recently, we've been talking about implementing an HDFS proxy (HADOOP-4575) 
> which would be a secure way to make HFTP/HSFTP available. In so doing, we may 
> even remove HFTP/HSFTP from being offered on the HDFS itself (that's another 
> discussion).
> In the case of the HDFS proxy, does it make sense to do away with the 
> artificial HFTP/HSFTP protocols, and instead simply offer standard HTTP and 
> HTTPS? That would allow non-HDFS-specific clients, as well as using various 
> standard HTTP infrastructure, such as load balancers, etc.
> NB, to the best of my knowledge, HFTP is only documented on the 
> [distcp|http://hadoop.apache.org/core/docs/current/distcp.html] page, and 
> HSFTP is not documented at all?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to