Fix BigQuery source alias deprecation warning (#12327) #12337
+85
−0
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.
Resolves #12327
Problem
When users define BigQuery sources with dataset/project at the top level (valid aliases for schema/database), dbt-core emits a false PropertyMovedToConfigDeprecation warning stating the property should be moved into config. This regression appeared after #12291 introduced alias-aware JSON schema validation.
Solution
Add a scoped guard in JSON schema validation to treat dataset and project as valid top-level source aliases when the active adapter includes BigQuery, preventing the incorrect deprecation warning. The guard only applies to sources[] paths, so other objects and adapters continue to warn appropriately. Added unit coverage for BigQuery source alias cases and a non‑BigQuery control.
Checklist