You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fabian Paul (Jira)" <ji...@apache.org> on 2022/03/01 07:51:00 UTC

[jira] [Created] (FLINK-26416) Release Testing:

Fabian Paul created FLINK-26416:
-----------------------------------

             Summary: Release Testing: 
                 Key: FLINK-26416
                 URL: https://issues.apache.org/jira/browse/FLINK-26416
             Project: Flink
          Issue Type: Improvement
          Components: Connectors / Common
    Affects Versions: 1.15.0
            Reporter: Fabian Paul
             Fix For: 1.15.0


With the introduction of Sink V2, the operator model of the sink changed slightly therefore it makes sense to test different upgrade/sanity scenarios.

 

You can take any of the existing Sinks in the project. I would recommend the FileSink.

 
 # Run a job with Flink 1.14 and take a savepoint and try to restore and resume with 1.15


 # Run a job with Flink 1.15 and take a savepoint and try to restore and resume with 1.15


 # Run a bounded job with Flink 1.15

 

In all cases, please verify that all records have been written at the end of the scenario and there are no duplicates.

 

 

 

 

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)