Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4344
@tzulitai Could you close this PR since its subsumed by #4357?
---
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
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4344
Ah, I thought you meant something else. Because this is pretty much the bug
this PR is trying to solve, right? ð
---
If your project is set up for it, you can reply to this email and have your
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4344
@aljoscha the issue is that there may be missing partitions when querying
partitions from Kafka (e.g., if some brokers are down).
---
If your project is set up for it, you can reply to this email
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4344
So partitions can be removed, in Kafka?
---
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/4344
For this change, I think we also need to verify how the consumers behave
when some restored partition is no longer reachable. (since previously, no
longer reachable partitions will be filtered out
