[BEAM-6087] ElasticsearchIO.write() retry functionality consumes response

• Type: Bug
• Status: Resolved
• Priority: P1
• Resolution: Duplicate
• Affects Version/s: 2.8.0
• Fix Version/s: Not applicable
• Component/s: io-java-elasticsearch
• Assignee: Etienne Chauchot
• Reporter: Damien Hollis
• Created: 18/Nov/18 20:28
• Updated: 16/May/20 13:29
• Resolved: 20/Nov/18 16:33

Description

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.