[
https://issues.apache.org/jira/browse/HADOOP-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510786
]
Owen O'Malley commented on HADOOP-1568:
---------------------------------------
Actually, we need to subclass the reader from HADOOP-1563 to be specific for
HDFS anyways, because we need the attributes to be available. In particular, we
need file size, replication, block size, and modification time. If we are
defining a format for tools to parse, I'd much rather use xml than http,
because it is far more appropriate for that use.
> 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
>
> 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.
