You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2023/04/17 09:42:00 UTC

[jira] [Updated] (FLINK-31121) KafkaSink should be able to catch and ignore exp via config on/off

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

Martijn Visser updated FLINK-31121:
-----------------------------------
    Fix Version/s:     (was: 1.18.0)

> KafkaSink should be able to catch and ignore exp via config on/off
> ------------------------------------------------------------------
>
>                 Key: FLINK-31121
>                 URL: https://issues.apache.org/jira/browse/FLINK-31121
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>    Affects Versions: 1.17.0
>            Reporter: Jing Ge
>            Assignee: Fang Yong
>            Priority: Major
>              Labels: pull-request-available
>
> It is a common requirement for users to catch and ignore exp while sinking the event to to downstream system like Kafka. It will be convenient for some use cases, if Flink Sink can provide built-in functionality and config to turn it on and off, especially for cases that data consistency is not very important or the stream contains dirty events. [1][2]
> First of all, consider doing it for KafkaSink. Long term, a common solution that can be used by any connector would be even better.
>  
> [1][https://lists.apache.org/thread/wy31s8wb9qnskq29wn03kp608z4vrwv8]
> [2]https://stackoverflow.com/questions/52308911/how-to-handle-exceptions-in-kafka-sink
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)