Problemsby IbisTrouble with BigQuery fail
Data engineering3 posts from 3 people3d active+22 posts in the last 7 days, 1 the 7 days before (steady)
Posts per day
The posts behind it
3, newest first[1.x Bug] Unit tests fail with "protected to the package" for public models from a `restrict-access: true` package...unit test errors | passes | | `protected` input from a `restrict-access` package | model fails to parse (correct) | unchanged | | `private` input, unit test on a model in the same group | passes | passes | | `private` input, model in another group | model fails to parse...dbt-labs/dbt · blazzdesar-login5Open ↗[1.x Bug] Contracted microbatch models fail on data_type aliases (e.g. float, string)...with dbt? bigquery ### Additional Context Reproduced on both BigQuery and Postgres. Workaround: override `bigquery__format_column` and `bigquery__get_empty_schema_sql` in the root project so they call `api.Column.translate_type` on the data type themselves. Changing the YAML...dbt-labs/dbt · mWekkingOpen ↗[v2 Bug] [BigQuery] Unit tests on incremental models fail with "Unrecognized name: _PARTITIONTIME" when expect is empty or format: sql...existing relation. Related open issue: #14383 (pseudo-columns in `SELECT *` expansion). Workaround: give `expect` rows as a dict with explicit columns. For tests that expect an empty result we found no workaround: `rows: []` and `format: sql` both fail. Impact: this blocks...dbt-labs/dbt · danielmolnar992Open ↗
Companies and products named
About this problem
Evidence
3 posts from 3 people in 1 place, about 2 a week over 9 days. Mostly on dbt-labs/dbt. Tools named alongside: dbt, PostgreSQL, DuckDB.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about BigQuery with no known issue, sharing the word "fail". First post Oct 11, 2026, latest Oct 19, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other BigQuery problems
History
Trouble with BigQuery fail (3 posts)