Return-Path: 
 <common-issues-return-75588-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 E97D917E33
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Wed, 14 Jan 2015 21:13:33 +0000 (UTC)
Received: (qmail 5117 invoked by uid 500); 14 Jan 2015 21:13:35 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 5067 invoked by uid 500); 14 Jan 2015 21:13:35 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 5056 invoked by uid 99); 14 Jan 2015 21:13:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jan 2015 21:13:35 +0000
Date: Wed, 14 Jan 2015 21:13:35 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12767543.1421267849000.85124.1421270015136@Atlassian.JIRA>
In-Reply-To: <JIRA.12767543.1421267849000@Atlassian.JIRA>
References: <JIRA.12767543.1421267849000@Atlassian.JIRA>
 <JIRA.12767543.1421267849518@arcas>
Subject: [jira] [Commented] (HADOOP-11480) Typo in hadoop-aws/index.md uses
 wrong scheme for test.fs.s3.name
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-11480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277688#comment-14277688 ] 

Hadoop QA commented on HADOOP-11480:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12692318/hadoop-11480-001.patch
  against trunk revision 7fe0f25.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc 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 2.0.3) 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-tools/hadoop-aws.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5403//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5403//console

This message is automatically generated.

> Typo in hadoop-aws/index.md uses wrong scheme for test.fs.s3.name
> -----------------------------------------------------------------
>
>                 Key: HADOOP-11480
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11480
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: hadoop-11480-001.patch
>
>
> Around line 270:
> {code}
>        <property>
>          <name>test.fs.s3.name</name>
>         <value>s3a://test-aws-s3/</value>
>        </property>
> {code}
> The scheme should be s3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)