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 2021/08/16 15:12:00 UTC

[jira] [Updated] (FLINK-23814) Test FLIP-143 KafkaSink

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

Fabian Paul updated FLINK-23814:
--------------------------------
    Description: 
The following scenarios are worthwhile to test
 * Start simple job with None/At-least once delivery guarantee and write records to kafka topic
 * Start simple job with exactly-once delivery guarantee and write records to kafka topic. The records should only be visible with a `read-committed` consumer
 * Stop a job with exactly-once delivery guarantee and restart it with different parallelism (scale-down, scale-up)
 * Restart/kill a taskmanager while writing in exactly-once mode

  was:
The following scenarios are worthwhile to test
 * Start simple job with None/At-least once delivery guarantee and write records to kafka topic
 * Start simple job with exactly-once delivery guarantee and write records to kafka topic. The records should only be visible with a `read-committed` consumer
 * Stop a job with exactly-once delivery guarantee and restart it with different parallelism (scale-down, scale-up)


> Test FLIP-143 KafkaSink
> -----------------------
>
>                 Key: FLINK-23814
>                 URL: https://issues.apache.org/jira/browse/FLINK-23814
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Connectors / Kafka
>            Reporter: Fabian Paul
>            Priority: Blocker
>             Fix For: 1.14.0
>
>
> The following scenarios are worthwhile to test
>  * Start simple job with None/At-least once delivery guarantee and write records to kafka topic
>  * Start simple job with exactly-once delivery guarantee and write records to kafka topic. The records should only be visible with a `read-committed` consumer
>  * Stop a job with exactly-once delivery guarantee and restart it with different parallelism (scale-down, scale-up)
>  * Restart/kill a taskmanager while writing in exactly-once mode



--
This message was sent by Atlassian Jira
(v8.3.4#803005)