Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 18 Jan 2016 08:37:39 +0000 (UTC)
From: "Liu Shaohui (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12932096.1453106227000.137568.1453106259795@Atlassian.JIRA>
In-Reply-To: <JIRA.12932096.1453106227000@Atlassian.JIRA>
References: <JIRA.12932096.1453106227000@Atlassian.JIRA>
 <JIRA.12932096.1453106227100@arcas>
Subject: [jira] [Created] (HDFS-9656) Hadoop-tools jars should be included
 in the classpath of hadoop command
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Liu Shaohui created HDFS-9656:
---------------------------------

             Summary: Hadoop-tools jars should be included in the classpath of hadoop command
                 Key: HDFS-9656
                 URL: https://issues.apache.org/jira/browse/HDFS-9656
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Liu Shaohui
            Assignee: Liu Shaohui
             Fix For: 3.0.0


Currently, jars under Hadoop-tools dir are not be included in the classpath of hadoop command. So we will fail to execute cmds about wasb or s3 file systems.

{quote}
$ ./hdfs dfs -ls wasb://demo@demo.blob.core.windows.net/
ls: No FileSystem for scheme: wasb
{quote}

A simple solution is to add those jars into the classpath of the cmds. Suggestions are welcomed~


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