You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/03/23 21:51:25 UTC
[jira] [Resolved] (HADOOP-12721) Hadoop-tools jars should be
included in the classpath of hadoop command
[ https://issues.apache.org/jira/browse/HADOOP-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HADOOP-12721.
---------------------------------------
Resolution: Won't Fix
HADOOP-12857 should have effectively fixed this issue for trunk in a fairly safe, generic way. Closing as won't fix.
> Hadoop-tools jars should be included in the classpath of hadoop command
> -----------------------------------------------------------------------
>
> Key: HADOOP-12721
> URL: https://issues.apache.org/jira/browse/HADOOP-12721
> Project: Hadoop Common
> Issue Type: Wish
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Attachments: HDFS-9656-v1.patch
>
>
> 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)