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 2018/07/10 14:59:00 UTC

[jira] [Updated] (HADOOP-15592) AssumedRoleCredentialProvider to propagate connection settings of S3A FS

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

Steve Loughran updated HADOOP-15592:
------------------------------------
    Summary: AssumedRoleCredentialProvider to propagate connection settings of S3A FS  (was: AssumedRoleProvider to propagate connection settings of S3A FS)

> AssumedRoleCredentialProvider to propagate connection settings of S3A FS
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-15592
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15592
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.1.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>
> The Assumed Role stuff of HADOOP-15141 doesn't pass down the various timeout options to the STS connection it builds up. That's OK For testing, but not in production, not if things play up (or you want to set a proxy).
> Proposed: we will have to use that painful builder API so as to be able to set the aws client config up



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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