[jira] [Updated] (BEAM-13288) Improve logging when BQ sink gets "No rows present in request" errors from BQ

["Chamikara Madhusanka Jayalath (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chamikara Madhusanka Jayalath updated BEAM-13288:
-------------------------------------------------
    Summary: Improve logging when BQ sink gets "No rows present in request" errors from BQ  (was: Improve logging when BQ sink get "No rows present in request" errors from BQ)

> Improve logging when BQ sink gets "No rows present in request" errors from BQ
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-13288
>                 URL: https://issues.apache.org/jira/browse/BEAM-13288
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp
>            Reporter: Chamikara Madhusanka Jayalath
>            Priority: P1
>
> These errors usually mean that a BQ streaming insert request with large rows did not not have enough time to JSON serialize the data hence corresponding HTTP request timing out resulting in a zero row request being sent to BQ.
> The workaround will be to increase the timeout below (or disable the timeout by setting the timeout to zero).
> [https://github.com/apache/beam/blob/9a934b7c62f5dee31cdb9a65ca3a79e83996281c/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryOptions.java#L46]
> We should detect such errors and add logging so that users can proactively try to increase the timeout.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)