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

["Fabian Paul (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-26416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504209#comment-17504209 ] 

Fabian Paul edited comment on FLINK-26416 at 3/10/22, 11:58 AM:
----------------------------------------------------------------

I mean if you build a user program with 1.14 it should also be executable with 1.15. From the error messages, it looks like you have used the same user program but updated the connector version to 1.15. Can you verify that the wrong FileSink connector version is used?


was (Author: fabian.paul):
I mean if you build a user program with 1.14 it should also be executable with 1.15. From the error messages, it looks like you have used the same user program but updated the connector version to 1.15. Can you verify that the wrong FileSink connector version is used?

> 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
>
>
> 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)