From hdfs-issues-return-24917-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org Fri Sep 9 16:27:32 2011 Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 638788D29 for ; Fri, 9 Sep 2011 16:27:32 +0000 (UTC) Received: (qmail 11045 invoked by uid 500); 9 Sep 2011 16:27:32 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 11015 invoked by uid 500); 9 Sep 2011 16:27:31 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 11007 invoked by uid 99); 9 Sep 2011 16:27:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2011 16:27:31 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2011 16:27:30 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 048398B6A2 for ; Fri, 9 Sep 2011 16:27:10 +0000 (UTC) Date: Fri, 9 Sep 2011 16:27:10 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1924158231.8718.1315585630015.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <209743167.24833.1315389790560.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-2316) webhdfs: a complete FileSystem implementation for accessing HDFS over HTTP MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101311#comment-13101311 ] Alejandro Abdelnur commented on HDFS-2316: ------------------------------------------ Would be OK if this prefix is optional/configurable as well as the capability of running the HTTP HDFS access in the DN in a different port (and by default is with the /webhdfs prefix in the same port as the rest of the HTTP services? > webhdfs: a complete FileSystem implementation for accessing HDFS over HTTP > -------------------------------------------------------------------------- > > Key: HDFS-2316 > URL: https://issues.apache.org/jira/browse/HDFS-2316 > Project: Hadoop HDFS > Issue Type: New Feature > Reporter: Tsz Wo (Nicholas), SZE > Assignee: Tsz Wo (Nicholas), SZE > > We current have hftp for accessing HDFS over HTTP. However, hftp is a read-only FileSystem and does not provide "write" accesses. > In HDFS-2284, we propose to have webhdfs for providing a complete FileSystem implementation for accessing HDFS over HTTP. The is the umbrella JIRA for the tasks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira