Damien Hollis created BEAM-6087:
-----------------------------------
Summary: ElasticsearchIO.write() retry functionality consumes
response
Key: BEAM-6087
URL: https://issues.apache.org/jira/browse/BEAM-6087
Project: Beam
Issue Type: Bug
Components: io-java-elasticsearch
Affects Versions: 2.8.0
Reporter: Damien Hollis
Assignee: Etienne Chauchot
Configuring retry functionality on ElasticsearchIO.write(), i.e.
{{ElasticsearchIO.write()}}
{{ .withRetryConfiguration(ElasticsearchIO.RetryConfiguration.create(3,
Duration.millis(30_000)))}}
Causes us to get this error when flushBundle is trying to checkForErrors
(specifically when parseResponse is trying to ready the response). The error
is:
{{Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: No
content to map due to end-of-input}}
The problem is that the retry functionality has already read the response. By
turning off the retry functionality, the problem is resolved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
