Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/2822
Merging ..
---
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
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2822
Makes sense.
+1 to this!
---
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
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/2822
Thanks for the review @StephanEwen. I'm pretty sure this doesn't affect the
normal Kinesis shard discovery. I'll give it some final tests before merging
(would like to get this in before the next
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/2822
I'm not entirely sure whether the fix is a good workaround, or whether we
should really bother with Kinesalite's incorrect behaviour at all in our
Kinesis connector.
I've considered the
