You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Robert Burke (Jira)" <ji...@apache.org> on 2020/12/07 23:38:00 UTC
[jira] [Updated] (BEAM-11309) Error handling in ElasticIO write
method
[ https://issues.apache.org/jira/browse/BEAM-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burke updated BEAM-11309:
--------------------------------
Fix Version/s: (was: 2.26.0)
> 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.3.4#803005)