fix(bigquery): separate auth project_id from destination project_id in Client#4171
Open
AnnasMazhar wants to merge 1 commit into
Open
fix(bigquery): separate auth project_id from destination project_id in Client#4171AnnasMazhar wants to merge 1 commit into
AnnasMazhar wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a BigQuery destination uses separate auth credentials (e.g. service account from project A to write to project B), the client initialization conflates both into a single project_id parameter, causing 404 Not Found errors.
This fix ensures the auth and destination project IDs are passed independently to the BigQuery client, matching the documented multi-project setup.
Closes #4160