hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eric baldeschwieler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-347) Implement HDFS content browsing interface
Date Thu, 06 Jul 2006 18:01:30 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-347?page=comments#action_12419573 ] 

eric baldeschwieler commented on HADOOP-347:
--------------------------------------------

Sounds good.

Could you provide a little more detail on the UI on the name node?  I image a link on the
front page to a page that redirects to a random data node.  That the plan?

Also you probably want to redirect the reader to a node containing the first block of the
file when you get the files contents.

The block viewing seems like a good option, we should also provide the ability to simply fetch
the full file.  Maybe two links on the directory browsing API could provide this option? 
Machine clients would be frustrated by the block structure.

Let's be sure to support tail (-f in the future).  The is very often the desired operation.
 A third link on the directory browsing page would do nicely.

I like the blocked view idea.  Perhaps all of this can simply be GET arguments appended to
the end of the URL?  IE "HDFS://x.com/myPath?sz=128k&off=512k"  Negative offsets could
be used for tail.

So you imagine a badge at the top of the block viewed page with <prev next> links? 
Might just add some block size options there too and tail.  Keep the whole API stateless (all
info in the URL).


> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message