ed Jun 16 12:27:43 2021
> *Recipients:*Yun Gao , user
> *Subject:*Re: Re: Upgrade job topology in checkpoint
>
>> We added a new sink to the job graph and redeployed - but the new sink
>> did not receive any records, as though it were not connected to the graph
>> (po
--
Sender:Padarn Wilson
Send Date:Wed Jun 16 12:27:43 2021
Recipients:Yun Gao , user
Subject:Re: Re: Upgrade job topology in checkpoint
We added a new sink to the job graph and redeployed - but the new sink did not
receive any records, as though it were not connected to the graph (possible it
-
> *Sender:*Padarn Wilson
> *Send Date:*Tue Jun 15 21:45:17 2021
> *Recipients:*Yun Gao
> *Subject:*Re: Upgrade job topology in checkpoint
>
>> Thanks Yun,
>>
>> Yes we do indeed retain checkpoints, but we were unable to restore with
>> new topology from
Hi Padarn,
By default the checkpoint would be disposed when the job finished or failed,
they would be retained only when explicitly required [1].
From the implementation perspective I think users could be able to change
topology when restored
from external checkpoint, but I think Flink would not
Hi all,
I'm looking for some clarity about changing job topology as described here:
https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/upgrading/#application-topology
My question is simple: Does this only apply to savepoints? Or can it also
work for checkpoints? (also why if no
