You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/04 18:23:00 UTC

[jira] [Commented] (BEAM-11309) Error handling in ElasticIO write method

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

Danny McCormick commented on BEAM-11309:
----------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/20639

> Error handling in ElasticIO write method
> ----------------------------------------
>
>                 Key: BEAM-11309
>                 URL: https://issues.apache.org/jira/browse/BEAM-11309
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-elasticsearch
>    Affects Versions: 2.25.0
>            Reporter: Lionel Setan
>            Priority: P3
>
> ElasticIO write method could sometimes raise Elastic internal errors, like invalid mapping, too many request or other. In this case, it can be usefull to retrieve uncommitted documents into output PCollection to isolate them. What the best way to achieve this ? Could it be implemented directly into ElasticIO connector ?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)