You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2017/03/22 20:32:41 UTC
[jira] [Commented] (HIVE-16276) Fix NoSuchMethodError:
com.amazonaws.services.s3.transfer.TransferManagerConfiguration.setMultipartUploadThreshold(I)V
[ https://issues.apache.org/jira/browse/HIVE-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937068#comment-15937068 ]
Edward Capriolo commented on HIVE-16276:
----------------------------------------
One thing to consider. What will the effect for people who already have non shaded s3 jars in their classpath. When the system looks up s3://xyz which implementation will they get?
> Fix NoSuchMethodError: com.amazonaws.services.s3.transfer.TransferManagerConfiguration.setMultipartUploadThreshold(I)V
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-16276
> URL: https://issues.apache.org/jira/browse/HIVE-16276
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Attachments: HIVE-16276.1.patch, HIVE-16276.2.patch, HIVE-16276.3.patch
>
>
> The druid-handler is pulling in some com.amazonaws dependencies that conflict with the version that Hadoop is using. This causes the above exception to be thrown when running Hive against S3. This patch fixes the dependency issue by shading the aws dependencies in the druid artifacts. Unfortunately, I can't find a great way to add a test for this so it doesn't happen in the future. We will need some more robust S3-integration tests for that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)