ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Roberts (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8794) Ambari 1.7 doesn't ship with NativeS3FileSystem in hadoop/hive classpaths
Date Sun, 18 Jan 2015 17:05:34 GMT

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

Sean Roberts commented on AMBARI-8794:
--------------------------------------

That edit will break with an HDP ugprade or aws-java-sdk upgrade.

Switching to this path should work across updates:
/usr/hdp/current/hadoop-mapreduce-client/aws-java-sdk-*.jar

Though I'm curious the best practice for updating the classpath(s) in a programatic way to
give a consistent way of configuring during automated deployments.

> Ambari 1.7 doesn't ship with NativeS3FileSystem in hadoop/hive classpaths
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-8794
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8794
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Dalsass Nicolas
>            Priority: Minor
>
> The latest release of ambari doesn't include in its default classpath NativeS3FileSystem
(which is now in hadoop-aws, and no longer in hadoop-common).
> For example, trying 
> hadoop distcp <localfile> <s3n://file> 
> will fail with a ClassNotFoundException.
> It also affects Hive external tables.



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

Mime
View raw message