When implementing #1230, we realised that the dbt compile command outputs the select statements related to models and transformations, but not necessarily the remaining relevant parts of the query (including creates, updates, inserts, drops).
This logic lives partially in dbt-core code and partially in the dbt adaptors of interest.
[ ] Analyse the possibility of, during the dbt compile - or somewhere related, to a setup task - to pre-create the full queries that we want to run with the async operators afterwards.
Context
When implementing #1230, we realised that the
dbt compile
command outputs the select statements related to models and transformations, but not necessarily the remaining relevant parts of the query (including creates, updates, inserts, drops).This logic lives partially in dbt-core code and partially in the dbt adaptors of interest.
Could we leverage the
--empty
flag (https://github.com/dbt-labs/dbt-core/issues/8980#issue-1973161545) in any way?Acceptance criteria
dbt compile
- or somewhere related, to a setup task - to pre-create the full queries that we want to run with the async operators afterwards.