[
https://issues.apache.org/jira/browse/HADOOP-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105747#comment-15105747
]
Chris Nauroth commented on HADOOP-12721:
----------------------------------------
When I code reviewed HADOOP-11485, I tested it by writing my own shell profile
to add the Azure jars to the default classpath. This was only ~5 lines of code.
https://issues.apache.org/jira/browse/HADOOP-11485?focusedCommentId=14308135&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14308135
Perhaps we could address this by shipping the distro with a library of commonly
useful shell profiles (azure, s3a, etc.). They would be inactive by default
for backwards-compatibility, but users could activate them quickly and easily
by copying or symlinking.
> 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://d...@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)
