Is there any example for dagster + dbt incremental loadas where the incrementals map to dagsters partitions? Does the reconciliation sensor work aut-magically in such a secenario? Or is the manual definition of partitioned asset jobs a requirement?

hi @geoHeil! the

load_assets_from...

functions support both a

partitions_def

and a

partition_keys_to_vars

function, which allows you to map between a partition key and some variables to pass into your incremental models. This does require that all models loaded with that command share the same partitioning, so you may need to load your dbt assets across multiple invocations of

load_assets_from...

if some assets are partitioned and others are non-partitioned

But this means that the reconciliation should work magically when the individual dbt assets are loaded with a sufficient partitioning strategy?

yep! the reconciliation sensor will treat the partitioned dbt assets the same as any other partitioned asset (and same for dagit)

I.e. The partitions tab for adhoc/ reconciliation does not exist