[
https://issues.apache.org/jira/browse/HADOOP-15642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-15642:
------------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
Status: Resolved (was: Patch Available)
done.
Regarding the process, we're getting familiar with the troublespots, aren't we?
* behaviour changes which sneak through the functional tests but which surface
in production, often obvservable in logged messages.
* deprecation quirks
* accidental dependency propagation
That's why the emphasis is on doing some CLI runs alongside automated testing.
Anything more people want to add, feel free.
> Update aws-sdk version to 1.11.375
> ----------------------------------
>
> Key: HADOOP-15642
> URL: https://issues.apache.org/jira/browse/HADOOP-15642
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build, fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
> Fix For: 3.2.0
>
> Attachments: HADOOP-15642-001.patch, HADOOP-15642-003.patch, Screen
> Shot 2018-07-30 at 14.11.22.png
>
>
> Move to a later version of the AWS SDK library for a different set of
> features and issues.
> proposed version: 1.11.375
> One thing which doesn't work on the one we ship with is the ability to create
> assumed role sessions >1h, as there's a check in the client lib for
> role-duration <= 3600 seconds. I'll assume more recent SDKs delegate duration
> checks to the far end.
> see:
> [https://aws.amazon.com/about-aws/whats-new/2018/03/longer-role-sessions/]
> * assuming later versions will extend assumed role life, docs will need
> changing,
> * Adding a test in HADOOP-15583 which expects an error message if you ask for
> a duration of 3h; this should act as the test to see what happens.
> * think this time would be good to explicitly write down the SDK update
> process
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
