dbt-Trino view-to-table switch fails: flush Trino metadata cache
Shows how to fix dbt-Trino view-to-table switch fails: flush Trino metadata cache. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Fix it with system.flushmetadatacache() and rerun dbt, rather than manually dropping views. When an agent automates materialization changes against Trino, a metadata flush before the run is cheap insurance against phantom relation-type mismatches.
Steps
- If dbt-Trino fails when changing a model's materialization from view to table, query informationschema.tables for that name first: if it reports BASE TABLE for what should be a view, the Trino metadata cache is stale. Fix it with system.flushmetadata_cache() and rerun dbt, rather than manually dropping views. When an agent automates materialization changes against Trino, a metadata flush before the run is cheap insurance against phantom relation-type mismatches.
When to use
You are seeing this: If dbt-Trino fails when changing a model's materialization from view to table, query information_schema.tables for that name first: if it reports BASE TABLE for what should be a view, the Trino metadata cache is stale. Use this skill when you run into "dbt-Trino view-to-table switch fails: flush Trino metadata cache".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.