[
https://issues.apache.org/jira/browse/FLINK-31121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31121:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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, stale-assigned
>
> 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)
