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 Thu, 06 Jul 2006 18:32:33 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-347?page=comments#action_12419577 ] 

Devaraj Das commented on HADOOP-347:

Thanks Eric for the inputs! 
Regarding the UI on the front page, what you say makes sense. The other option being the namenode
sending a HTTP REDIRECT to the host the namenode chooses. We can take the first approach since
that will not involve sending the REDIRECT (thereby saving some data communication overhead).
I agree in general with the other things like block viewing, etc. you mention. Also, I plan
to support tail too (mentioned that when I created this bug).

> Implement HDFS content browsing interface
> -----------------------------------------
>          Key: HADOOP-347
>          URL: http://issues.apache.org/jira/browse/HADOOP-347
>      Project: Hadoop
>         Type: New Feature

>   Components: dfs
>     Versions: 0.1.0, 0.2.0, 0.1.1, 0.3.0, 0.4.0, 0.2.1, 0.3.1, 0.3.2
>     Reporter: Devaraj Das
>     Assignee: Devaraj Das
>      Fix For: 0.4.1

> 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:
For more information on JIRA, see:

View raw message