hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1568) NameNode Schema for HttpFileSystem
Date Fri, 31 Aug 2007 20:49:18 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524187
] 

Doug Cutting commented on HADOOP-1568:
--------------------------------------

> 2. Is HftpFileSystem a typo?

No.  It's not generic access to filesystems over HTTP (as I attempted in HADOOP-1563) but
rather access to the Hadoop FileSystem feature set over HTTP.  We couldn't specify 'http'
as the URI's scheme, since the actual URL accessed doesn't match this.  The HftpFileSystem
implementation translates the hftp: URIs to HTTP URLs accessing two servlets, one for directory
listings and another for file content.

The purpose of all this is to provide a version-independent means to access HDFS filesystems,
for back-compatiblity.  So, if you're running two clusters and only upgrade one, but wish
them to be able to access one another, this should let you.  This protocol is simple-enough
that we don't expect it to change incompatibly, unlike HDFS's internal protocols, which change
regularly.

> NameNode Schema for HttpFileSystem
> ----------------------------------
>
>                 Key: HADOOP-1568
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1568
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Chris Douglas
>            Assignee: Chris Douglas
>             Fix For: 0.14.0
>
>         Attachments: 1568-6.patch, compat.patch, xmlenc-0.52.jar
>
>
> This issue will track the design and implementation of (the first pass of) a servlet
on the namenode for querying its filesystem via HTTP. The proposed syntax for queries and
responses is as follows.
> *Query*
> {noformat}GET http://<nn>:<port>/ls.jsp[<?option>[&option]*] HTTP/1.1{noformat}
> Where _option_ may be any of the following query parameters:
> _path_ : String (default: '/')
> _recursive_ : boolean (default: false)
> _filter_ : String (default: none)
> *Response*
> The response will be returned as an XML document in the following format:
> {noformat}
> <listing path="..." recursive="(yes|no)" filter="..."
>          time="yyyy-MM-dd hh:mm:ss UTC" version="...">
>   <directory path="..."/>
>   <file path="..." modified="yyyy-MM-dd hh:mm:ss" blocksize="..."
>         replication="..." size="..."
>         dnurl="http://dn:port/streamFile?..."/>
> </listing>
> {noformat}

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


Mime
View raw message