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

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

commit 695372cd0a5bece795d1248f32e46ec9748a40e8
Author: Dawid Wysakowicz <[email protected]>
AuthorDate: Thu Feb 3 12:25:07 2022 +0100

    [FLINK-21752] Add a call to TypeSerializer#duplicate in migration tests
    
    We should verify that a TypeSerializer even after migration can be
    safely duplicated. In order to do that we can duplicate a new serializer
    in the TypeSerializerUpgradeTestBase before we try to use for
    deserialization.
---
 .../flink/api/common/typeutils/TypeSerializerUpgradeTestBase.java  | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git 
a/flink-core/src/test/java/org/apache/flink/api/common/typeutils/TypeSerializerUpgradeTestBase.java
 
b/flink-core/src/test/java/org/apache/flink/api/common/typeutils/TypeSerializerUpgradeTestBase.java
index 9751e2d..f319528 100644
--- 
a/flink-core/src/test/java/org/apache/flink/api/common/typeutils/TypeSerializerUpgradeTestBase.java
+++ 
b/flink-core/src/test/java/org/apache/flink/api/common/typeutils/TypeSerializerUpgradeTestBase.java
@@ -431,8 +431,13 @@ public abstract class 
TypeSerializerUpgradeTestBase<PreviousElementT, UpgradedEl
         if (!isRestoreSerializer) {
             TypeSerializerSnapshot<T> snapshot = 
writeAndThenReadSerializerSnapshot(serializer);
             TypeSerializer<T> restoreSerializer = snapshot.restoreSerializer();
+            serializedData =
+                    readAndThenWriteData(
+                            serializedData, restoreSerializer, 
restoreSerializer, testDataMatcher);
+
+            TypeSerializer<T> duplicateSerializer = 
snapshot.restoreSerializer().duplicate();
             readAndThenWriteData(
-                    serializedData, restoreSerializer, restoreSerializer, 
testDataMatcher);
+                    serializedData, duplicateSerializer, duplicateSerializer, 
testDataMatcher);
         }
     }
 

Reply via email to