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/10 13:46:00 UTC

[jira] [Closed] (FLINK-26416) Release Testing: Sink V2 sanity checks

     [ https://issues.apache.org/jira/browse/FLINK-26416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabian Paul closed FLINK-26416.
-------------------------------

> Release Testing: Sink V2 sanity checks
> --------------------------------------
>
>                 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
>            Assignee: Liu
>            Priority: Blocker
>              Labels: release-testing
>             Fix For: 1.15.0
>
>         Attachments: image-2022-03-10-18-58-19-519.png, image-2022-03-10-20-36-17-977.png, image-2022-03-10-20-36-45-974.png, image-2022-03-10-20-48-19-744.png, image-2022-03-10-20-51-25-331.png, image-2022-03-10-20-55-46-224.png
>
>
> 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)