[flink] branch release-1.8 updated: [FLINK-15863][docs] Fix docs stating that savepoints are relocatable

[nk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

nkruber pushed a commit to branch release-1.8
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.8 by this push:
     new 3f307fb  [FLINK-15863][docs] Fix docs stating that savepoints are relocatable
3f307fb is described below

commit 3f307fb02b5844936d973ce519f86d1fd9d8fe49
Author: bdine <ba...@gmail.com>
AuthorDate: Tue Feb 4 13:13:50 2020 +0100

    [FLINK-15863][docs] Fix docs stating that savepoints are relocatable
---
 docs/ops/upgrading.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/ops/upgrading.md b/docs/ops/upgrading.md
index 0955127..a562563 100644
--- a/docs/ops/upgrading.md
+++ b/docs/ops/upgrading.md
@@ -159,12 +159,12 @@ Besides operator uids, there are currently two *hard* preconditions for job migr
 `semi-asynchronous` mode. In case your old job was using this mode, you can still change your job to use 
 `fully-asynchronous` mode before taking the savepoint that is used as the basis for the migration.
 
-2. 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..
-
+2. Another **important** precondition is that all the savepoint data must be accessible from the new installation 
+under the same (absolute) path. 
+This also includes access to any additional files that are referenced from inside the 
+savepoint file (the output from state backend snapshots).
+Any savepoint data is currently referenced by absolute paths inside the meta data file and thus a savepoint is 
+not relocatable via typical filesystem operations.
 
 ### STEP 1: Take a savepoint in the old Flink version.