dawidwys closed pull request #7102: [FLINK-10767][docs] Updated savepoint 
compatibility matrix with 1.7
URL: https://github.com/apache/flink/pull/7102
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/ops/upgrading.md b/docs/ops/upgrading.md
index eb00a2b28c6..0451940723e 100644
--- a/docs/ops/upgrading.md
+++ b/docs/ops/upgrading.md
@@ -212,6 +212,7 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
       <th class="text-center">1.4.x</th>
       <th class="text-center">1.5.x</th>
       <th class="text-center">1.6.x</th>
+      <th class="text-center">1.7.x</th>
       <th class="text-center">Limitations</th>
     </tr>
   </thead>
@@ -224,6 +225,7 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
           <td class="text-center"></td>
           <td class="text-center"></td>
           <td class="text-center"></td>
+          <td class="text-center"></td>
           <td class="text-left">The maximum parallelism of a job that was 
migrated from Flink 1.1.x to 1.2.x+ is
           currently fixed as the parallelism of the job. This means that the 
parallelism can not be increased after
           migration. This limitation might be removed in a future bugfix 
release.</td>
@@ -236,6 +238,7 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
           <td class="text-center">O</td>
           <td class="text-center">O</td>
           <td class="text-center">O</td>
+          <td class="text-center">O</td>
           <td class="text-left">When migrating from Flink 1.2.x to Flink 
1.3.x+, changing parallelism at the same
           time is not supported. Users have to first take a savepoint after 
migrating to Flink 1.3.x+, and then change
           parallelism. Savepoints created for CEP applications cannot be 
restored in 1.4.x+.</td>
@@ -248,6 +251,7 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
           <td class="text-center">O</td>
           <td class="text-center">O</td>
           <td class="text-center">O</td>
+          <td class="text-center">O</td>
           <td class="text-left">Migrating from Flink 1.3.0 to Flink 1.4.[0,1] 
will fail if the savepoint contains Scala case classes. Users have to directly 
migrate to 1.4.2+ instead.</td>
     </tr>
     <tr>
@@ -258,6 +262,7 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
           <td class="text-center">O</td>
           <td class="text-center">O</td>
           <td class="text-center">O</td>
+          <td class="text-center">O</td>
           <td class="text-left"></td>
     </tr>
     <tr>
@@ -268,6 +273,7 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
           <td class="text-center"></td>
           <td class="text-center">O</td>
           <td class="text-center">O</td>
+          <td class="text-center">O</td>
           <td class="text-left"></td>
     </tr>
     <tr>
@@ -278,6 +284,18 @@ Savepoints are compatible across Flink versions as 
indicated by the table below:
           <td class="text-center"></td>
           <td class="text-center"></td>
           <td class="text-center">O</td>
+          <td class="text-center">O</td>
+          <td class="text-left"></td>
+    </tr>
+    <tr>
+          <td class="text-center"><strong>1.7.x</strong></td>
+          <td class="text-center"></td>
+          <td class="text-center"></td>
+          <td class="text-center"></td>
+          <td class="text-center"></td>
+          <td class="text-center"></td>
+          <td class="text-center"></td>
+          <td class="text-center">O</td>
           <td class="text-left"></td>
     </tr>
   </tbody>


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to