[
https://issues.apache.org/jira/browse/BEAM-13288?focusedWorklogId=689617&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-689617
]
ASF GitHub Bot logged work on BEAM-13288:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Dec/21 21:31
Start Date: 02/Dec/21 21:31
Worklog Time Spent: 10m
Work Description: chamikaramj merged pull request #16096:
URL: https://github.com/apache/beam/pull/16096
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 689617)
Time Spent: 40m (was: 0.5h)
> Improved 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
> Assignee: John Casey
> Priority: P1
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)
