Github user zsxwing commented on the issue:
    > We do need to handle it comparing completely different topicpartitions, 
because it's entirely possible to have a job with a single topicpartition A, 
which is deleted or unsubscribed, and then single topicpartition B is added, in 
the space of one batch.
    Yeah, it's also possible that when a batch is running, a single 
topicpartition C is created then deleted. But the Kafka source doesn't even 
know C. The root issue is currently the approach is polling metadata, and any 
metadata changes between two pollings are missing.

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 or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to