For the record here, I created an issue FLINK-35477
<https://issues.apache.org/jira/browse/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
> <https://github.com/apache/flink-connecto
esn’t check if the subscription already exists anymore.
On Thu, May 23, 2024 at 4:31 PM Igor Basov wrote:
> Hi everyone,
>
> I have a problem with how Flink deals with the existing subscription in a
> Pulsar topic.
>
>- Subscription has some accumulated backlog
>- F
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
production_ready/#set-uuids-for-all-operators
>
>
> On Fri, May 7, 2021 at 10:13 PM Igor Basov wrote:
>
>> Hello,
>> I got confused about usage of savepoints and checkpoints in different
>> scenarios.
>> I understand that checkpoints' main purpose is fault
Hello,
I got confused about usage of savepoints and checkpoints in different
scenarios.
I understand that checkpoints' main purpose is fault tolerance, they are
more lightweight and don't support changing job graph, parallelism or state
backend when restoring from them, as mentioned in the latest 1
