[
https://issues.apache.org/jira/browse/HDFS-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105706#comment-15105706
]
Allen Wittenauer commented on HDFS-9656:
----------------------------------------
-1
1) Adding hadoop-tools to the default path is going to break all sorts of
user-level things due to the amount of transitive dependencies.
2) This will *greatly* impact the startup of time of commands by including a
bunch of class files that will never get used.
bq. A simple solution is to add those jars into the classpath of the cmds.
Suggestions are welcomed~
Instead of slamming in everything, users should be using shell profiles to
include the jars they actually need. Another thing that would be good to do is
to break up the hadoop tools dir to be per component.
> 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
> 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://[email protected]/
> 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)
