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 not)
By default the checkpoint would be disposed when the job finished or failed,
they would be retained only when explicitly required .
From the implementation perspective I think users could be able to change topology when restored
from external checkpoint, but I think Flink would not guarantee this functionality.
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 was a code bug, but I was trying to understand if this make sense given the implementation)
re-including mailing list, excluded by accident
From the current description it seems to me that the issue does not related to
the state ? I think we may first check if the operator logic is right and whether
the precedent tasks have indeed emitted records to the new sink.
Agreed, it seemed unlikely to be state, I just wanted to confirm that this was unexpected before ruling it out.
On Thu, Jun 17, 2021 at 10:45 AM Yun Gao <[hidden email]> wrote:
|Free forum by Nabble
|Edit this page