Repository navigation
BigQuery insertAll always retries operation #3321
Copy link
Copy link
Closed
Labels
🚨 criticalP0 critical issue. Requires immediate fixP0 critical issue. Requires immediate fixapi: bigqueryIssues related to the BigQuery API.Issues related to the BigQuery API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Activity
- addedtype: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.api: bigqueryIssues related to the BigQuery API.Issues related to the BigQuery API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.
on May 30, 2018 Hi @neuromantik33,
Thanks for catching this issue! Would you mind turning your commit into a pull request? For testing, one option could be to add a unit test to
BigQueryImplTest.java, set a spy on theBigQueryOptions options(see line 274), and assert thatgetRetrySettings()is called on that spy object whenBigQueryImpl.insertAllis run or not run.- added🚨 criticalP0 critical issue. Requires immediate fixP0 critical issue. Requires immediate fix
on Nov 25, 2018 - removed🚨 criticalP0 critical issue. Requires immediate fixP0 critical issue. Requires immediate fixpriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.
on Dec 3, 2018 - added a commit that references this issue
on Dec 3, 2018 - addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.and removedtype: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.
on Dec 4, 2018 - added🚨 criticalP0 critical issue. Requires immediate fixP0 critical issue. Requires immediate fix
on Dec 4, 2018 - added a commit that references this issue
on Dec 4, 2018 - added a commit that references this issue
on Feb 3, 2019 - added a commit that references this issue
on Mar 9, 2026 - added 4 commits that reference this issue
on Mar 24, 2026
Metadata
Metadata
Assignees
Labels
🚨 criticalP0 critical issue. Requires immediate fixP0 critical issue. Requires immediate fixapi: bigqueryIssues related to the BigQuery API.Issues related to the BigQuery API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Hi. First time reporter here.
I wanted to report a small but perhaps inconvenient bug in BigQuery, specifically regarding streaming inserts using an
InsertAllRequest. It seems for some reason unknown to me that inserts are retried using the client'sRetrySettingswhenever row ids are supplied for deduplication.When the current implementation always attempts a retry (which I discovered during these odd retry errors) due to the fact that
Lists.transform()is strictly lazy.Anyhow the fix is minor and I corrected it on my branch but I'm unsure how to write the necessary tests in order to validate my claim. My commit is here: neuromantik33@984b5bb, and after proper review I can submit a pull request.
Thanks in advance for any feedback.