Hi Emily
One workaround that might help is to leverage the state-processor-api[1].
You would have to do some upfront work to create a state-processor job to
wipe the state (offsets) of the topic you want to remove and use the newly
generated savepoint without the removed state of the topic or topi
Hi there
It would be helpful if you could include the code for your pipeline. One
suggestion, can you disable the "EXACTLY_ONCE" semantics on the producer.
Using EXACTLY_ONCE will leverage Kafka transactions and thus add overhead.
I would disable it to see if you still get the same situation.
Als
Hi Theo
In your initial email, you mentioned that you have "a bit of Data on it"
when referring to your topic with ten partitions. Correct me if I'm wrong,
but that sounds like the data in your topic is bounded and trying to test a
streaming use-case. What kind of parallelism do you have configure
