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/07/11 16:49:00 UTC

[jira] [Comment Edited] (FLINK-30998) Add optional exception handler to flink-connector-opensearch

    [ https://issues.apache.org/jira/browse/FLINK-30998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742098#comment-17742098 ] 

Martijn Visser edited comment on FLINK-30998 at 7/11/23 4:48 PM:
-----------------------------------------------------------------

Fixed in:

apache/flink-connector-opensearch:main d853e3d6be3e0f15e25c1220800b7d5fcf152c43
apache/flink-connector-opensearch:v1.0 TODO


was (Author: martijnvisser):
Fixed in:

apache/flink-connector-opensearch:main d853e3d6be3e0f15e25c1220800b7d5fcf152c43
apache/flink-connector-opensearch:v3.0 TODO

> Add optional exception handler to flink-connector-opensearch
> ------------------------------------------------------------
>
>                 Key: FLINK-30998
>                 URL: https://issues.apache.org/jira/browse/FLINK-30998
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Opensearch
>    Affects Versions: 1.16.1
>            Reporter: Leonid Ilyevsky
>            Assignee: Leonid Ilyevsky
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: opensearch-1.0.2
>
>
> Currently, when there is a failure coming from Opensearch, the FlinkRuntimeException is thrown from OpensearchWriter.java code (line 346). This makes the Flink pipeline fail. There is no way to handle the exception in the client code.
> I suggest to add an option to set a failure handler, similar to the way it is done in elasticsearch connector. This way the client code has a chance to examine the failure and handle it.
> Here is the use case example when it will be very useful. We are using streams on Opensearch side, and we are setting our own document IDs. Sometimes these IDs are duplicated; we need to ignore this situation and continue (this way it works for us with Elastisearch).
> However, with opensearch connector, the error comes back, saying that the batch failed (even though most of the documents were indexed, only the ones with duplicated IDs were rejected), and the whole flink job fails.



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