I have migrated topic-v1 with 10 partitions to topic-v2, with 100 partitions.
I have a stateless exactly-once kafka stream currently reading from topic-v1, and wish to update the stream to read from topic-v2 instead. Given the different number of partitions, is there any way to do this at the Kafka level without violating exactly-once? One potential solution at the application level, is for the new stream to check if the old stream has already run on the input message, and skip it if it has. Any other ideas? Regards, Raman
