Hi Jan, As of now Flink does not give any guarantees for Table/SQL API savepoint compatibility if you change the query or Flink version. Flink Table/SQL API uses an optimizer that can apply different optimizations or operations reordering based on the queried fields or computations that can result in a completely different physical plan.
Generally speaking you should be fine when adding/removing fields in a projection. I'd say it is the only somewhat safe change, but it is not guaranteed in all cases nevertheless. Best, Dawid On 01/03/2021 17:41, Jan Oelschlegel wrote: > > Hi at all, > > > > i would like to know how far a state schema evolution is possible by > using SQL API of Flink. Which query changes can I do without > disrupting the schema of my savepoint? > > > > > > In the documentation is, only for the DataStream API , written what > are the do’s and don’ts regarding a safe schema evolution. [1] > > > > > > [1] > https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/schema_evolution.html > <https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/schema_evolution.html> > > > > > > > > Best, > > Jan > > > > HINWEIS: Dies ist eine vertrauliche Nachricht und nur für den > Adressaten bestimmt. Es ist nicht erlaubt, diese Nachricht zu kopieren > oder Dritten zugänglich zu machen. Sollten Sie diese Nachricht > irrtümlich erhalten haben, bitte ich um Ihre Mitteilung per E-Mail > oder unter der oben angegebenen Telefonnummer.
OpenPGP_signature
Description: OpenPGP digital signature