[
https://issues.apache.org/jira/browse/FLINK-23814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405110#comment-17405110
]
Hang Ruan commented on FLINK-23814:
-----------------------------------
Fine, I will test the KafkaSink again after fix the scale-down situation.
I don't reproduce the data loss problem in
https://issues.apache.org/jira/browse/FLINK-23896 by the supplied test cases.
After reading the issue, I still don't get the point about it. :(
> 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
> Assignee: Hang Ruan
> Priority: Blocker
> Labels: release-testing
> 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)
