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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/05/06 16:54:12 UTC
[jira] [Commented] (HADOOP-13062) S3A Introspect to invoke
incompatible AWS TransferManagerConfiguration methods
[ https://issues.apache.org/jira/browse/HADOOP-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274342#comment-15274342 ]
Steve Loughran commented on HADOOP-13062:
-----------------------------------------
Looking at the patch for HADOOP-12269, this is not a minor one-method has changed kind of problem; there's a lot that has changed. I don't believe we can fix this.
> S3A Introspect to invoke incompatible AWS TransferManagerConfiguration methods
> ------------------------------------------------------------------------------
>
> Key: HADOOP-13062
> URL: https://issues.apache.org/jira/browse/HADOOP-13062
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.7.2
> Reporter: Steve Loughran
>
> The AWS SDK changed the signature of the {{TransferManagerConfiguration.setMultipartUploadThreshold}}, moving one param from an int to a long. This is fixed at compile time, so S3a built against the old library doesn't link to to the new one, and vice versa —something leading to problems downstream.
> It may be possible to use reflection to make this binding, at least on the 2.7 branch, so that dropping in to a later SDK doesn't break things
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org