[
https://issues.apache.org/jira/browse/FLINK-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber resolved FLINK-15863.
---------------------------------
Fix Version/s: 1.9.3
1.8.4
Resolution: Fixed
Fixed via:
* master: 7ef6eb45ce65baff20061a50c312118031a19f1b
* release-1.10: bf722e7b3c0a1f9d43e685a8a7657405f3959226
* release-1.9: e4eb30362d0a8902b8bb958137064e8456342ced
* release-1.8: 3f307fb02b5844936d973ce519f86d1fd9d8fe49
> Fix docs stating that savepoints are relocatable
> ------------------------------------------------
>
> Key: FLINK-15863
> URL: https://issues.apache.org/jira/browse/FLINK-15863
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 1.9.2, 1.10.0
> Reporter: Nico Kruber
> Assignee: Bastien DINE
> Priority: Blocker
> Labels: pull-request-available, usability
> Fix For: 1.8.4, 1.11.0, 1.9.3, 1.10.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This section from
> https://ci.apache.org/projects/flink/flink-docs-stable/ops/upgrading.html#preconditions
> states that savepoints are relocatable which they are not yet (see
> FLINK-5763). It should be fixed and/or removed; I'm unsure what change from
> 1.3 it should actually reflect.
> {quote}Another important precondition is that for savepoints taken before
> Flink 1.3.x, all the savepoint data must be accessible from the new
> installation and reside under the same absolute path. Before Flink 1.3.x, the
> savepoint data is typically not self-contained in just the created savepoint
> file. Additional files can be referenced from inside the savepoint file (e.g.
> the output from state backend snapshots). Since Flink 1.3.x, this is no
> longer a limitation; savepoints can be relocated using typical filesystem
> operations..{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
