[
https://issues.apache.org/jira/browse/FLINK-26751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvid Heise closed FLINK-26751.
-------------------------------
Resolution: Won't Fix
As stated, with the current async sink design, it's not possible to implement
an EOS sink. If we ever extend the async sink, we can reopen the ticket.
Note that async sink is a means to reduce boilerplate for "easy" sinks that do
not require a sophisticated state management, in particular sinks that just do
some API calls to write data in either a fire-and-forget or retry-until-success
fashion. We would probably overengineer the interface if we also want to
capture the various EOS flavors. It's wiser to add more base implementations of
{{Sink}} in the future when multiple EOS sinks share common code (e.g., Pulsar
and Kafka).
> [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)
