Re: Pulsar connector resets existing subscription

Yes, I think you're right. This bug appeared after we switched from the Pulsar Admin API to the Pulsar Client API. Currently, the connector doesn't check the existing subscription position. I apologize for this regression. We need to add tests and implement a fix. Since this is relatively easy to a

Re: Pulsar connector resets existing subscription

For the record here, I created an issue FLINK-35477 regarding this. On Mon, May 27, 2024 at 1:21 PM Igor Basov wrote: > Ok, believe the breaking changes were introduced in this commit >

Re: Pulsar connector resets existing subscription

Ok, believe the breaking changes were introduced in this commit . Here

Pulsar connector resets existing subscription

Hi everyone, I have a problem with how Flink deals with the existing subscription in a Pulsar topic. - Subscription has some accumulated backlog - Flink job is deployed from a clear state (no checkpoints) - Flink job uses the same subscription name as the existing one; the start curso