-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WriteToBigQuery ignores insert_retry_strategy on HttpErrors #21080
Comments
Hey Danny, |
Hey @nervoussidd you can find our contribution guide here - https://beam.apache.org/contribute/ For future reference, you can self assign issues by commenting |
I am having trouble finding the higher level function that will handle this re-raised exception. Would anyone be able to point that out for me? I haven't found where that exception would lead to retry strategy evaluation. Doing some research on this one and finding that the Those errors will raise a |
.take-issue |
This issue has been resolved with MR 28091. |
@ajdub508 you can close this issue by commenting ".close-issue" and a bot will close it |
.close-issue |
insertAll
will retry forever on a streaming pipeline running on2.31.0
, withinsert_retry_strategy=RetryStrategy.RETRY_NEVER
, andcreate_disposition=BigQueryDisposition.CREATE_NEVER
.Found while testing error handling for a pipeline by writing to a table that doesn't exist, ending up with no element in
BigQueryWriteFn.FAILED_ROWS
and these errors repeated in the logs:Possibly related to BEAM-12362. Had been running on
2.29.0
previously, which would send errors repeatedly with no trace:2.31.0
is logging the errors but ignores retry strategy, preventing errors from being handled throughFailedRows
tag.Imported from Jira BEAM-12783. Original Jira may contain additional context.
Reported by: ajdub980a.
The text was updated successfully, but these errors were encountered: