[
https://issues.apache.org/jira/browse/FLINK-26751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510301#comment-17510301
]
Fabian Paul commented on FLINK-26751:
-------------------------------------
The Async Sink is designed to only guarantee at-least-once guarantee and the
external system is responsible to deduplicate. In the case of Kafka, this is
not a good idea because Kafka offers a dedicated transaction mechanism that can
be used to implement a full two-phase commit guaranteeing exactly-once
delivery.
[~almogtavor] do you already have a plan on how to guarantee exactly-once
delivery with the AsyncSink?
> [FLIP-171] Kafka implementation of AsyncSinkBase
> ------------------------------------------------
>
> Key: FLINK-26751
> URL: https://issues.apache.org/jira/browse/FLINK-26751
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Kafka
> Reporter: Almog Tavor
> Priority: Major
>
> *User stories:*
> Standardize the Kafka connector to implement AsyncSinkBase.
> *Scope:*
> * Implement an asynchronous sink for Kafka by inheriting the AsyncSinkBase
> class.
> h2. References
> More details to be found
> [https://cwiki.apache.org/confluence/display/FLINK/FLIP-171%3A+Async+Sink]
> h4.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
