These are the asset key's that I observe when providing the same key-prefix for both, when loading fivetran and dbt assets: fivetran asset <key-prefix>/<schema-name>/<tablename> dbt asset <dbt-source-name>/<tablename>

they both represent the same table. The dbt asset has all the lineage. The fivetran asset does not have any lineage

so my understanding is that the

snowflake_io_manager

could be the binding element between my assets imported form dbt and fivetran. But then when I initialize a storage manage it doesn't seem to get used. I'm testing that by providing it with wrong credentials and nothing fails and I also don't see any snowflake connections when providing correct credentials. My question remains - can I expect dagster to automatically detect the dbt downstream dependencies of my fivetran assets or do I need to manually create that relationship?

I found a (rather hacky) way of making it work. Not providing key prefixes and aligning the name of dbt source with the schema I guess produces a key naming match in dagster and my lineage between fivetran and dbt is automatically created.

two more observations: • when passing the same key_prefix to both the fivetran load and the dbt load the lineage is not created. It is only created when not passing a key prefix. • The storage_manager doesn't seem to play a role. Even when not passing a storage manager the lineage is created based on the key (when no prefix is used)

Any further insights would be appreciated - should the lineage be created leveraging the storage manger and actual schema and table names rather then matching on asset keys?