The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Anyone could share a functional project using `load_assets_from_dbt_manifest` with the `select`  argument?
We're trying to move out of `load_assets_from_dbt_project` because of loading times, but the transition is not easy.
I'd like to see if there are working examples somewhere before I can tell if the problems are in my head or in the library.

I can’t share an entire project, but I can share a few snippets. I’m assuming you’d like to see asset construction?

Thanks for your answer, Adam.
I'd like to see: loading the manifest, using load_assets_from_dbt_manifest with a select, and the dbt resource configuration.

In particular, it seems the `select` does not behave the same between `load_assets_from_dbt_project` and `load_assets_from_dbt_manifest`.

My select looks like `models/my_directory` as I want to load every model from a specific directory, this works fine with loading from project, but the same select doesn't work when loading from manifest.
I get this error message:
&gt; UserWarning: Error loading repository location load_from_manifest.py:dagster._core.errors.DagsterInvalidSubsetError: No dbt models match the selection string 'models/my_directory '.

That syntax looks a little off in general - have you tried it with just `dbt ls —-select`

I don’t think you want the `models/` portion

Nice, removing the `models/` indeed worked, thanks!
Though, this syntax is working with `dbt ls` and with `load_assets_from_dbt_project`, so there's an unexpected difference of behavior with `load_assets_from_dbt_manifest`.

fyi <@U01AV4K3W14> - maybe worth tracking this disparity