Repository navigation
BigQueryJob returns false if it does not exists #851
Copy link
Copy link
Closed
Labels
api: computeIssues related to the Compute Engine API.Issues related to the Compute Engine API.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
- addedapi: bigqueryIssues related to the BigQuery API.Issues related to the BigQuery API.
on Apr 4, 2016 Agree to the above though I would like to mention the other option of throwing an exception if we detect that this job no longer exists.
I think both of these options are better than getting an infinite loop by waiting for a non-existing job to complete.
- 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.
on Apr 4, 2016 Nice catch. FYI job information is no longer available after six months from job creation.
I think I would returntrueif you do not have any strong argument against.This issue also applies to compute's operations where operations can be deleted only if they have already completed their execution. Even for compute I would return
trueif the operation does not exist.Reacted by Arie- addedapi: computeIssues related to the Compute Engine API.Issues related to the Compute Engine API.and removedapi: bigqueryIssues related to the BigQuery API.Issues related to the BigQuery API.
on Apr 5, 2016 Leaving this open for compute
- added a commit that references this issue
on Jul 14, 2022 - added a commit that references this issue
on Jul 27, 2022 - added a commit that references this issue
on Aug 18, 2022 7 remaining items
- added a commit that references this issue
on Oct 5, 2022 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 30, 2026 - added a commit that references this issue
on Apr 1, 2026 - added 2 commits that reference this issue
on Apr 29, 2026
Metadata
Metadata
Assignees
Labels
api: computeIssues related to the Compute Engine API.Issues related to the Compute Engine API.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.
On line 183, the job return
falseif it isnull. It makes more sense for it to returntrue. A job once created cannot be deleted. If a user somehow obtained a non-nullJobinstance, the only way for this get to receivenullis that the job was completed and somehow perished./cc @aozarov @mziccard