[
https://issues.apache.org/jira/browse/BEAM-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431436#comment-17431436
]
Evan Galpin commented on BEAM-11309:
------------------------------------
[~lionelsetan] I believe this may be addressed after
[https://github.com/apache/beam/pull/15381] is contained in a release. Would
you be able to confirm?
> 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)
