hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13062) S3A Introspect to invoke incompatible AWS TransferManagerConfiguration methods
Date Tue, 26 Apr 2016 10:21:12 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-13062:
------------------------------------
    Issue Type: Improvement  (was: Sub-task)
        Parent:     (was: HADOOP-11694)

> 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: Improvement
>          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)

Mime
View raw message