Closed dannnnthemannnn closed 5 months ago
+1
+1
I am getting the same traceback when copying macros
from dbt-labs/dbt-external-tables as dbt-external-tables
folder into my project's macros.
This is the folder structure I have:
macros
├── add_rows_limit.sql
├── dbt-external-tables
│ ├── common
│ └── plugins
└── generate_schema_name.sql
Am I missing anything?
Did anyone make this work?
Seems like a connected issue too: https://github.com/dbt-labs/dbt-core/issues/4596
+1
in my experience, this issue is usually when you have a jinja variable in one of your models, but it does not have a default value, so when DBT tries to build the manifest, it fails.
i have no idea why it has this behaviour, but it is what it is i guess. make sure you have default values
This bug should no longer exist in the official implementation!
Materialized Views have been supported in dbt since dbt-core 1.7 (November 2023). See dbt docs: materialized views and dbt docs: Big Query configurations: materialized views for more information.
The version of materialized views in this experimental repo is is long-overdue for official deprecation -- it has not been meaningfully maintained or improved for over three years (see https://github.com/dbt-labs/dbt-labs-experimental-features/pull/11).
If you haven't already, you should try out the official implementation! Should you encounter an issue, you can then open bug or enhancement ticket on either dbt-core or the dbt-bigquery for your current data platform.
Here is the error I am getting by adding the default and bigquery folders to my macros folder: