Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-6087

ElasticsearchIO.write() retry functionality consumes response

    XMLWordPrintableJSON

    Details

      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.

        Attachments

          Activity

            People

            • Assignee:
              echauchot Etienne Chauchot
              Reporter:
              damien.hollis Damien Hollis
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: