[
https://issues.apache.org/jira/browse/NIFI-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812221#comment-15812221
]
ASF subversion and git services commented on NIFI-3153:
-------------------------------------------------------
Commit 1195d4c186ac1cba2e595c2068ea24d5f80fab19 in nifi's branch
refs/heads/master from [~jameswing]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1195d4c ]
NIFI-3153 Updating AWS SDK Version
This closes #1341.
> 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
>
> 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)
