Skip to content

Loading via write streams into Tables from Datasets with manually-specified project IDs returns invalid job #1345

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

Closed
1kilobit opened this issue Mar 27, 2024 · 0 comments · Fixed by #1346
Labels
api: bigquery Issues related to the googleapis/nodejs-bigquery API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@1kilobit
Copy link
Contributor

1kilobit commented Mar 27, 2024

Environment details

  • OS: Ubuntu 22.04.2 LTS
  • Node.js version: 20.2.0
  • npm version: 9.6.6
  • @google-cloud/bigquery version: 7.5.1

Steps to reproduce

  1. Create a load job from a file path on a Table from a Dataset with a manually-specified project ID
    await bq
      .dataset("datasetname", {projectId: "projectid"})
      .table("tablename")
      .load("filepath")
  2. Get error ApiError: Not Found: Job defaultprojectid:location.jobid despite load job actually getting created successfully in the actual project
@1kilobit 1kilobit added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Mar 27, 2024
@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/nodejs-bigquery API. label Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the googleapis/nodejs-bigquery API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant