fer to just point out this in documentation to say explicitly
> > Flink
> > > > does not guarantee such kind of backwards compatibility.
> > > >
> > > > Best
> > > > Yun Tang
> > > >
> > > > From:
t; > I prefer to just point out this in documentation to say explicitly
> Flink
> > > does not guarantee such kind of backwards compatibility.
> > >
> > > Best
> > > Yun Tang
> > >
> > > From: Ufuk Celebi
&g
explicitly Flink
> > does not guarantee such kind of backwards compatibility.
> >
> > Best
> > Yun Tang
> >
> > From: Ufuk Celebi
> > Sent: Wednesday, May 27, 2020 16:42
> > To: dev@flink.apache.org
> > Subject: Re
plicitly Flink
> does not guarantee such kind of backwards compatibility.
>
> Best
> Yun Tang
>
> From: Ufuk Celebi
> Sent: Wednesday, May 27, 2020 16:42
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] (Document) Backwards Compatibili
documentation to say explicitly Flink does
not guarantee such kind of backwards compatibility.
Best
Yun Tang
From: Ufuk Celebi
Sent: Wednesday, May 27, 2020 16:42
To: dev@flink.apache.org
Subject: Re: [DISCUSS] (Document) Backwards Compatibility of Savepoints
I
I agree with Konstantin and Steven that it makes sense to point this out
explicitly.
I think that the following would be helpful:
1/ Mention breaking compatibility in release notes
2/ Update the linked table to reflect compatibilities while pointing out
what the community commits to maintain goi
> A use case for this might be when you want to rollback a framework
upgrade (after some time) due to e.g. a performance
or stability issue.
Downgrade (that Konstantin called out) is an important and realistic
scenario. It will be great to support backward compatibility for savepoint
or at least d
Hi,
It might have been implicit choice, but so far we were not supporting the
scenario that you are asking for. It has never been tested and we have lot’s of
state migration code sprinkled among our code base (for example upgrading state
fields of the operators like [1]), that only supports upg
Hi everyone,
I recently stumbled across the fact that Savepoints created with Flink 1.11
can not be read by Flink 1.10. A use case for this might be when you want
to rollback a framework upgrade (after some time) due to e.g. a performance
or stability issue.
>From the documentation [1] it seems a
