GitHub user bowenli86 opened a pull request:
https://github.com/apache/flink/pull/4627
[FLINK-7422][kinesis] Upgrade Kinesis Client Library (KCL) and AWS SDK in
flink-connector-kinesis
## What is the purpose of the change
Upgrade KCL from 1.6.2 to 1.8.1
(https://mvnrepository.com/artifact/com.amazonaws/amazon-kinesis-client)
## Brief change log
#### KCL:
Upgrade KCL from 1.6.2 to 1.8.1
#### AWS SDK
Upgrade AWS SDK from 1.10.71 to 1.11.171
## Verifying this change
This change is already covered by existing tests, such as
*flink/flink-connectors/flink-connector-kinesis/src/test/java/org/apache/flink/streaming/connectors/kinesis/FlinkKinesisConsumerMigrationTest.java*.
I've also been using it in our production environment without any problems.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes)
## Documentation
- Does this pull request introduce a new feature? (no)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bowenli86/flink FLINK-7422
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4627.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4627
----
commit 7d59b06827a6b072a0e488ae0d5bac404b08c438
Author: Bowen Li <bowenl...@gmail.com>
Date: 2017-08-10T23:31:50Z
FLINK-7422 Upgrade Kinesis Client Library (KCL) and AWS SDK in
flink-connector-kinesis
commit 6386983239bd3024b395c865ec4fd33e232ca5a3
Author: Bowen Li <bowenl...@gmail.com>
Date: 2017-08-30T16:35:03Z
FLINK-7422 Upgrade Kinesis Client Library (KCL) and AWS SDK in
flink-connector-kinesis
commit 2cc26a127dd45f54a680167abe0ebb46193b97d2
Author: Bowen Li <bowenl...@gmail.com>
Date: 2017-08-30T16:42:37Z
Merge branch 'master' into FLINK-7422
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
