Hey team! :wave: I have a question about how the ...
# integration-dbt
m
Hey team! 👋 I have a question about how the
manifest.json
is being used in dagster. I am loading DBT assets from manifest and running them in a partitioned job. When I pull out compiled SQL via
runtime_metadata_fn
when running a back-fill (2 jobs concurrently is my current setup) I see the wrong partition key associated with an asset materialisation (the key is passed as a variable ) I have
use_build_command
set to True FWIW Do I need to enforce single runs when using the manifest ? I use the manifest because I need to pull out compiled SQL and use it as metadata (see here).
Just to add to this - the compiled code in the
DBT_TARGET_PATH
is as expected. The
node_info
object contains the incorrect data.