Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 0B9C5F2D3 for ; Wed, 27 Mar 2013 02:37:16 +0000 (UTC) Received: (qmail 74624 invoked by uid 500); 27 Mar 2013 02:37:15 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 74530 invoked by uid 500); 27 Mar 2013 02:37:15 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 74520 invoked by uid 99); 27 Mar 2013 02:37:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Mar 2013 02:37:15 +0000 Date: Wed, 27 Mar 2013 02:37:15 +0000 (UTC) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-9357) Fallback to default authority if not specified in FileContext 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/HADOOP-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614832#comment-13614832 ] Hadoop QA commented on HADOOP-9357: ----------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12575626/hadoop-9357-3.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/2368//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/2368//console This message is automatically generated. > Fallback to default authority if not specified in FileContext > ------------------------------------------------------------- > > Key: HADOOP-9357 > URL: https://issues.apache.org/jira/browse/HADOOP-9357 > Project: Hadoop Common > Issue Type: Bug > Reporter: Andrew Wang > Assignee: Andrew Wang > Priority: Minor > Fix For: 3.0.0 > > Attachments: hadoop-9357-1.patch, hadoop-9357-2.patch, hadoop-9357-3.patch > > > Currently, FileContext adheres rather strictly to RFC2396 when it comes to parsing absolute URIs (URIs with a scheme). If a user asks for a URI like "hdfs:///tmp", FileContext will error while FileSystem will add the authority of the default FS (e.g. turn it into "hdfs://defaultNN:port/tmp"). > This is technically correct, but FileSystem's behavior is nicer for users and okay based on 5.2.3 in the RFC, so lets do it in FileContext too: > {noformat} > For backwards > compatibility, an implementation may work around such references > by removing the scheme if it matches that of the base URI and the > scheme is known to always use the syntax. The parser > can then continue with the steps below for the remainder of the > reference components. Validating parsers should mark such a > misformed relative reference as an error. > {noformat} -- 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