GitHub user tony810430 opened a pull request:
https://github.com/apache/flink/pull/3994
[FLINK-6653] Avoid directly serializing AWS's Shard class in Kinesis
consumer's checkpoints
The proposal please refer to the comment on JIRA.
Thanks for contributing to Apache Flink. Before you open your pull request,
please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your
pull request. For more information and/or questions please refer to the [How To
Contribute guide](http://flink.apache.org/how-to-contribute.html).
In addition to going through the list, please provide a meaningful
description of your changes.
- [v] General
- The pull request references the related JIRA issue ("[FLINK-XXX] Jira
title text")
- The pull request addresses only one issue
- Each commit in the PR has a meaningful commit message (including the
JIRA id)
- [x] Documentation
- Documentation has been added for new functionality
- Old documentation affected by the pull request has been updated
- JavaDoc for public methods has been added
- [v] Tests & Build
- Functionality added by the pull request is covered by tests
- `mvn clean verify` has been executed successfully locally or a Travis
build has passed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tony810430/flink FLINK-6653
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3994.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 #3994
----
commit 9ebec3a7242cd225626a9e17bad4e315f9cbab53
Author: Tony Wei <[email protected]>
Date: 2017-05-25T02:39:22Z
[FLINK-6653] Avoid directly serializing AWS's Shard class in Kinesis
consumer's checkpoints
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
