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] [Created] (HADOOP-15076) s3a troubleshooting to add "things don't work after I dropped in a new AWS SDK JAR"
Date Thu, 30 Nov 2017 10:15:01 GMT
Steve Loughran created HADOOP-15076:
---------------------------------------

             Summary: s3a troubleshooting to add "things don't work after I dropped in a new
AWS SDK JAR"
                 Key: HADOOP-15076
                 URL: https://issues.apache.org/jira/browse/HADOOP-15076
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: documentation, fs/s3
    Affects Versions: 2.8.2
            Reporter: Steve Loughran


A recurrent theme in s3a-related JIRAs, support calls etc is "tried upgrading the AWS SDK
JAR and then I got the error ...". We know here "don't do that", but its not something immediately
obvious to lots of downstream users who want to be able to drop in the new JAR to fix things/add
new features

We need to spell this out quite clearlyi "you cannot safely expect to do this. If you want
to upgrade the SDK, you will need to rebuild the whole of hadoop-aws with the maven POM updated
to the latest version, ideally rerunning all the tests to make sure something hasn't broken.


Maybe near the top of the index.md file, along with "never share your AWS credentials with
anyone"




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message