The behavior described-dbt running the orders model as a view despite being explicitly configured as a table
-indicates that dbt is not correctly detecting or applying the model-level configuration during compilation.
dbt relies heavily on the target-path directory to write compiled SQL, manifest files, and run artifacts. If the target-path is misconfigured, pointing to a location that dbt does not handle correctly or that overlaps with another folder used internally, dbt may fail to load the correct configuration from the merged project settings.
When dbt cannot locate the compiled configuration for a model, it defaults to its standard materialization type, which is view. This explains why the logs show:
"Finished running 1 view model"
even though the dbt_project.yml clearly declares:
materialized: table.
Additionally, the logs indicate no warnings or parsing errors, meaning dbt ran successfully but with incorrect settings-another indicator of configuration metadata being overridden or misplaced due to an incorrect target- path.
By resolving the target-path issue, dbt will successfully load the model configuration and materialize the orders model as a table as intended.