You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/04/22 08:15:58 UTC

[jira] [Commented] (HADOOP-11863) Document process of deploying alternative file systems like S3 and Azure to the classpath.

    [ https://issues.apache.org/jira/browse/HADOOP-11863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506499#comment-14506499 ] 

Chris Nauroth commented on HADOOP-11863:
----------------------------------------

For more background, see this email thread on the user@ list:

http://mail-archives.apache.org/mod_mbox/hadoop-user/201504.mbox/%3CCA+XUwYxPxLkfhOxn1jNkoUKEQQMcPWFzvXJ=u+kP28KDEjO4GQ@mail.gmail.com%3E


> Document process of deploying alternative file systems like S3 and Azure to the classpath.
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11863
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11863
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Chris Nauroth
>
> Using the alternative {{FileSystem}} implementations like S3 and Azure requires that the relevant jars are made available on the runtime classpath for Hadoop processes.  In a typical distro layout, these jars are in the tools directory, and thus not part of the default classpath.  The process of making these jars available on the classpath needs to be documented more clearly.



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