If new partitions are added to a topic, connected KafkaSSE connections will not see that new partition. Connected clients will miss messages.

This is not a common problem, as partitions are rarely added to topics, but still, KafkaSSE should handle this. This is a consequence of the fact that KafkaSSE uses a 'low level' librdkafka consumer via the .assign method, rather than the 'high level' one via the .subscribe method. This was done to avoid saving state on the Kafka brokers for these types of connections.

To fix, KafkaSSE will likely need to periodically issue a getMetadata call, and refresh the assignments (and stored last-event-id) for a connected clients if the partition count changes.