Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 19239 invoked from network); 19 Jul 2006 10:48:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Jul 2006 10:48:26 -0000 Received: (qmail 59919 invoked by uid 500); 19 Jul 2006 10:48:25 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 59899 invoked by uid 500); 19 Jul 2006 10:48:25 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 59890 invoked by uid 99); 19 Jul 2006 10:48:25 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jul 2006 03:48:25 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jul 2006 03:48:24 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E93737141F4 for ; Wed, 19 Jul 2006 10:46:14 +0000 (GMT) Message-ID: <19884348.1153305974952.JavaMail.jira@brutus> Date: Wed, 19 Jul 2006 03:46:14 -0700 (PDT) From: "Devaraj Das (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-347) Implement HDFS content browsing interface In-Reply-To: <17227613.1152182310090.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/HADOOP-347?page=comments#action_12422085 ] Devaraj Das commented on HADOOP-347: ------------------------------------ By the way, in order to use this, hit the namenode's jetty (default port 50070). You will see the links from there. > 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.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 > Assigned To: Devaraj Das > Fix For: 0.5.0 > > Attachments: content_browsing.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