Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/2414
Thank you for opening a pull request to fix the issue.
I think we also need to cover another case: What happens when the number of
shards has been reduced in a resharding and some fetchers are now without a
shard? I think in that case, the worker also needs to emit a final
Long.MAX_VALUE, and it has to fail once it gets a shard assigned again.
---
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.
---
