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 alternative is to just use the
`describeStream(streamName)` variant, always fetching the whole shard list and
explicitly ruling out shards we've already seen. That'll make the code clean of
such "workarounds", but will be problematic for Kinesis users whose shard count
exceeds the largest number of shards the API can return.
---
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.
---
