Data & Analytics
A dbt parser change can turn a valid test into empty SQL
Compare compiled generic tests before enabling the dbt v2 parser on a production project.
November 11, 2026
An analytics team runs dbt test successfully, then adds --use-v2-parser and sees a warehouse syntax error. A dbt issue shows a generic test whose compiled query contains an empty subquery under the v2 parser, while the normal run passes. The customer problem is not only a failed CI job: the team no longer knows whether its data-quality checks have equivalent meaning.
Compare artifacts, not only exit codes
Run the same selected test with and without the parser flag in a clean environment. Save the exact dbt and adapter versions, compiled SQL, manifest entry, and error. The report used dbt 1.12.6 and a Databricks adapter; do not generalize it to every project. dbt’s data-test guide explains that generic tests are parameterized SQL assertions and pass when their query returns zero failing rows. An empty inner query is therefore a compilation defect, not a passing assertion.
Add one canary test for each custom generic-test pattern in the project, including package-provided tests. Compare test selection, compiled SQL and outcomes. A test that disappears from selection and a test that generates invalid SQL require different fixes.
Gate parser adoption
Keep the current parser for production while reproducing the gap and checking upstream status. dbt’s comparison guide describes --use-v2-parser as a way to test compatibility without interrupting production workflows. Make that the rollout contract: no production switch until critical tests compile and run with the same intended assertion.
Adovo’s view
Faster parsing is valuable only if the guardrails still guard. A data test is a business promise expressed as SQL. Preserve the promise through the migration, then take the speed improvement.
