[jira] [Updated] (NIFI-3153) Update AWS SDK

["Pierre Villard (JIRA)" <ji...@apache.org>]

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

Pierre Villard updated NIFI-3153:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0
           Status: Resolved  (was: Patch Available)

Full build with contrib check. +1
Merged to master, thanks [~jameswing]!

> Update AWS SDK
> --------------
>
>                 Key: NIFI-3153
>                 URL: https://issues.apache.org/jira/browse/NIFI-3153
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: James Wing
>            Assignee: James Wing
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> I propose to update NiFi's AWS SDK to v1.11.68 (December 16, 2016) or later to get support for recent AWS updates:
> * New Regions - ap-south-1 (Mumbai), ca-central-1 (Canada), eu-west-2 (London), us-east-2 (Ohio)
> * New AWS services
> NiFi's current SDK is v1.11.8 (June 16, 2016).  I looked through the [AWS SDK for Java release notes|https://aws.amazon.com/releasenotes/Java?browse=1] to search for upgrade complications.  Most of the changes look fine -- mostly new services, regions, and simple bug fixes.   I found one item of interest:
> * New [Retry Throttling|https://aws.amazon.com/blogs/developer/introducing-retry-throttling/] feature has been made the default rather than optional starting in [v1.11.12|https://aws.amazon.com/releasenotes/Java/2878241577606051].  It looks very sensible to not flog the system pointlessly if requests are already failing, and I  expect it to be a benefit for most NiFi/AWS use cases.  However, it is the kind of sneaky behavioral change I was looking for.



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