fix: ensure dbt BigQueryConfig dataset & project are set#5526
Merged
newtonapple merged 1 commit intomainfrom Oct 10, 2025
Merged
fix: ensure dbt BigQueryConfig dataset & project are set#5526newtonapple merged 1 commit intomainfrom
newtonapple merged 1 commit intomainfrom
Conversation
georgesittas
approved these changes
Oct 10, 2025
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.
DBT BigQuery config aliases
project->databaseanddataset->schema. And more importantly, they should always be the same. A profiles.yaml config with onlyschemaspecified can referencetarget.datasetin jinja templates and will throw an error since we don't currently setdatasetin the config.