You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Executing dbt seed fails if the Dremio space does not exist already. This is because it tries to create the seed view before creating the Dremio space.
Creating the Dremio space manually and re-running dbt seed succeeds.
Expected Behavior
Executing dbt seed should succeed even if the Dremio space does not already exist.
Steps To Reproduce
Create a new project with a seed targeting a Dremio space that does not already exist.
by default twin_strategy = clone : for a materialization leading to a table Relation, a proxy view selecting from the table is (re)created in the corresponding custom folder based on the default and custom database+schema confs and the possibly overriden custom macros. But this is a 'light' view created by the adapter, not a regular dbt model. So dbt does not know at startup that it has to check if the view's path exists and create it overwise.
For time being, you can try to :
set the twin_strategy to prevent or allow (not the default clone)
and create a real model materialized as a view ontop if you really need it.
The only problem is for tables not in standard parquet/iceberg format. Indeed, the 'light' view reuse the write formating configuration of the underlying table to build the select with the good read formating options.
Is there an existing issue for this?
Current Behavior
Executing
dbt seed
fails if the Dremio space does not exist already. This is because it tries to create the seed view before creating the Dremio space.Creating the Dremio space manually and re-running
dbt seed
succeeds.Expected Behavior
Executing
dbt seed
should succeed even if the Dremio space does not already exist.Steps To Reproduce
dbt seed
.Environment
Relevant log output
No response
The text was updated successfully, but these errors were encountered: