Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B901DEC46 for ; Wed, 6 Mar 2013 18:42:14 +0000 (UTC) Received: (qmail 45695 invoked by uid 500); 6 Mar 2013 18:42:13 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 45594 invoked by uid 500); 6 Mar 2013 18:42:13 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 45282 invoked by uid 99); 6 Mar 2013 18:42:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 18:42:13 +0000 Date: Wed, 6 Mar 2013 18:42:13 +0000 (UTC) From: "Plamen Jeliazkov (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-4559) WebHDFS does not allow resolution of Symlinks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Plamen Jeliazkov created HDFS-4559: -------------------------------------- Summary: WebHDFS does not allow resolution of Symlinks Key: HDFS-4559 URL: https://issues.apache.org/jira/browse/HDFS-4559 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.0.3-alpha Reporter: Plamen Jeliazkov Assignee: Plamen Jeliazkov Fix For: 3.0.0, 2.0.4-beta WebHDFS allows you to create symlinks via the CREATESYMLINK operation, but the GETFILEINFO operation specifically calls the getFileInfo() method of the NameNodeRpcServer which does not resolve symlinks. I propose adding a parameter to GETFILEINFO such that if true will call getFileLinkInfo() rather than getFileInfo() which will resolve any symlinks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira