hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-347) Implement HDFS content browsing interface
Date Sat, 14 Oct 2006 02:49:15 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-347?page=comments#action_12442170 ] 
Devaraj Das commented on HADOOP-347:

   [[ Old comment, sent by email on Fri, 7 Jul 2006 00:08:28 +0530 ]]

Hi Eric,
I spoke to Marco regarding WebDAV, and he told me that he just got started
on the work, etc. So I am wondering whether I should start off on this work
without WebDAV. Things like block view, etc. may not be possible with WebDAV
without major tweaking. What are your thoughts?

> Implement HDFS content browsing interface
> -----------------------------------------
>                 Key: HADOOP-347
>                 URL: http://issues.apache.org/jira/browse/HADOOP-347
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.4.0, 0.3.2, 0.3.1, 0.3.0, 0.2.1, 0.2.0, 0.1.1, 0.1.0
>            Reporter: Devaraj Das
>         Assigned To: Devaraj Das
>             Fix For: 0.5.0
>         Attachments: content_browsing.patch, fsnamesystem.patch
> Implement HDFS content browsing interface over HTTP. Clients would connect to the NameNode
and this would send a redirect to a random DataNode. The DataNode, via dfs client, would proxy
to namenode for metadata browsing and to other datanodes for content. One can also view the
local blocks on any DataNode. Head, Tail will be provided as shorthands for viewing the first
block and the last block of a file. 
> For full file viewing, the data displayed per HTTP request will be a block with a PREV/NEXT
link. The block size for viewing can be a configurable parameter (the user sets it via the
web browser) to the HTTP server (e.g., 256 KB can be the default block size for viewing files).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message