Hi!

I have run into a weird issue which I could have sworn that it wouldnt
happen :D
I feel there was a discussion about this in the past but maybe im wrong,
but I hope someone can point me to a ticket.

Lets say you create a kafka consumer that consumes (t1,t2,t3), you take a
savepoint and deploy a new version that only consumes (t1).

The restore logic now still starts to consume (t1,t2,t3) which feels very
unintuitive as those were explicitly removed from the list. It is also hard
to debug as the topics causing the problem are not defined anywhere in your
job, configs etc.

Has anyone run into this issue? Should we change this default behaviour or
at least have an option to not do this?

Cheers,
Gyula

Reply via email to