Return-Path: X-Original-To: apmail-hama-dev-archive@www.apache.org Delivered-To: apmail-hama-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EAAEF18C62 for ; Thu, 25 Feb 2016 13:47:22 +0000 (UTC) Received: (qmail 51114 invoked by uid 500); 25 Feb 2016 13:47:22 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 49707 invoked by uid 500); 25 Feb 2016 13:47:18 -0000 Mailing-List: contact dev-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list dev@hama.apache.org Received: (qmail 49666 invoked by uid 99); 25 Feb 2016 13:47:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Feb 2016 13:47:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0D7632C033A for ; Thu, 25 Feb 2016 13:47:18 +0000 (UTC) Date: Thu, 25 Feb 2016 13:47:18 +0000 (UTC) From: "Cazen Lee (JIRA)" To: dev@hama.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HAMA-984) Support AWS S3 schema in Hadoop 2.6+ MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Cazen Lee created HAMA-984: ------------------------------ Summary: Support AWS S3 schema in Hadoop 2.6+ Key: HAMA-984 URL: https://issues.apache.org/jira/browse/HAMA-984 Project: Hama Issue Type: Improvement Components: build Reporter: Cazen Lee Hadoop 2.6+ does not contain AWS S3 related filesystem by default. So, IOException(No FileSystem for scheme) occurred while trying to access S3 via s3 or s3n schema. I know it's not a Hama bug but it will be helpful to Hama users who using AWS S3 because it can be used by previous version(includes 1.x) without manual setting. Of course, we can also guide through the changes, without modification any source code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)