[ https://issues.apache.org/jira/browse/FLINK-32028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797103#comment-17797103 ]
Weijie Guo commented on FLINK-32028: ------------------------------------ main via 40774fad0f4ecd1a0d104dcb339e6bb860b0a4bf. > Error handling for the new Elasticsearch sink > --------------------------------------------- > > Key: FLINK-32028 > URL: https://issues.apache.org/jira/browse/FLINK-32028 > Project: Flink > Issue Type: Improvement > Components: Connectors / ElasticSearch > Affects Versions: elasticsearch-3.0.0 > Reporter: Tudor Plugaru > Assignee: Peter Schulz > Priority: Major > Labels: pull-request-available > Fix For: elasticsearch-3.1.0 > > > The deprecated ElasticsearchSink supports setting an error handler via a > [public method > |https://github.com/apache/flink-connector-elasticsearch/blob/8f75d4e059c09b55cc3a44bab3e64330b1246d27/flink-connector-elasticsearch7/src/main/java/org/apache/flink/streaming/connectors/elasticsearch7/ElasticsearchSink.java#L216] > but the new sink, does not. > Ideally there would be a way to handle ES specific exceptions and be able to > skip items from being retried on ES indefinitely and not block entirely the > pipeline. -- This message was sent by Atlassian Jira (v8.20.10#820010)