Hi Dan,
currently, we cannot provide any savepoint guarantees between releases.
Because of the nature of SQL that abstracts away runtime operators, it
might be that a future execution plan will look completely different and
thus we cannot map state anymore. This is not avoidable because the
optimizer might get smarter when adding new optimizer rules.
For such cases, we recommend to dry out the old pipeline and/or warm up
a new pipeline with historic data when upgrading Flink. A change in
columns sometimes works but even this depends on the used operators.
Regards,
Timo
On 18.01.21 04:46, Dan Hill wrote:
How well does Flink SQL work with checkpoints and savepoints? I tried
to find documentation for it in v1.11 but couldn't find it.
E.g. what happens if the Flink SQL is modified between releases? New
columns? Change columns? Adding joins?
