[ 
https://issues.apache.org/jira/browse/HADOOP-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687951#comment-15687951
 ] 

Chris Nauroth commented on HADOOP-13050:
----------------------------------------

[~liuml07], thank you for reviewing.

{quote}
One last concern from the Jenkins run is that, HADOOP-13727 added the 
SharedInstanceProfileCredentialsProvider, which can be removed after this AWS 
SDK upgrade. Do you think we address it here, or separately?
{quote}

I'd suggest handling it in a separate JIRA, targeted only to 3.x (not 2.x).  
It's possible that users of 2.8 will start referring to 
{{SharedInstanceProfileCredentialsProvider}} in their configuration.  If it 
were removed in 2.9, then those configurations would break after a user 
upgrades from 2.8 to 2.9.  Waiting until 3.x for that kind of change would 
adhere to our compatibility guidelines and give those users more of a warning.

> Upgrade to AWS SDK 10.11+
> -------------------------
>
>                 Key: HADOOP-13050
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13050
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build, fs/s3
>    Affects Versions: 2.7.2
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Blocker
>         Attachments: HADOOP-13050-001.patch, HADOOP-13050-002.patch, 
> HADOOP-13050-branch-2-003.patch, HADOOP-13050-branch-2-004.patch, 
> HADOOP-13050-branch-2.002.patch, HADOOP-13050-branch-2.003.patch
>
>
> HADOOP-13044 highlights that AWS SDK 10.6 —shipping in Hadoop 2.7+, doesn't 
> work on open jdk >= 8u60, because a change in the JDK broke the version of 
> Joda time that AWS uses.
> Fix, update the JDK. Though, that implies updating http components: 
> HADOOP-12767.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to