> Out of curiosity, does it mean that savepoint created by flink 1.11 cannot be recovered by a job running with flink 1.10 or older versions (so downgrade is impossible)?
That's correct. See the mailing list thread on Backwards Compatibility of Savepoints [1]. [1] http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Document-Backwards-Compatibility-of-Savepoints-td41903.html On Tue, Mar 2, 2021 at 4:39 PM XU Qinghui <qinghui...@polytechnique.edu> wrote: > Out of curiosity, does it mean that savepoint created by flink 1.11 cannot > be recovered by a job running with flink 1.10 or older versions (so > downgrade is impossible)? > > Le mar. 2 mars 2021 à 12:25, David Anderson <dander...@apache.org> a > écrit : > >> You are correct in thinking that the documentation wasn't updated. If you >> look at the master docs [1] you will see that they now say >> >> Can I move the Savepoint files on stable storage? # >> <https://ci.apache.org/projects/flink/flink-docs-master/docs/ops/state/savepoints/#can-i-move-the-savepoint-files-on-stable-storage> >> >> The quick answer to this question is currently “yes”. Sink Flink 1.11.0, >> savepoints are self-contained and relocatable. You can move the file and >> restore from any location. >> >> >> If you want more detail than the quick answer, see [2]. >> >> Best, >> David >> >> [1] >> https://ci.apache.org/projects/flink/flink-docs-master/docs/ops/state/savepoints/#can-i-move-the-savepoint-files-on-stable-storage >> [2] https://issues.apache.org/jira/browse/FLINK-19381 >> >> On Tue, Mar 2, 2021 at 10:33 AM Farouk <farouk.za...@gmail.com> wrote: >> >>> Hi >>> >>> Does this chapter is outdated with Flink 1.11 ? >>> >>> >>> https://ci.apache.org/projects/flink/flink-docs-release-1.12/ops/state/savepoints.html#can-i-move-the-savepoint-files-on-stable-storage >>> >>> *Can I move the Savepoint files on stable storage?* >>> >>> *The quick answer to this question is currently “no” because the meta >>> data file references the files on stable storage as absolute paths for >>> technical reasons. The longer answer is: if you MUST move the files for >>> some reason there are two potential approaches as workaround. First, >>> simpler but potentially more dangerous, you can use an editor to find the >>> old path in the meta data file and replace them with the new path. Second, >>> you can use the class SavepointV2Serializer as starting point to >>> programmatically read, manipulate, and rewrite the meta data file with the >>> new paths.* >>> >>> >>> <https://ci.apache.org/projects/flink/flink-docs-release-1.12/ops/state/savepoints.html#top> >>> >>> Thanks >>> Farouk >>> >>