https://dagster.io/ logo
#integration-airbyte
Title
# integration-airbyte
m

Mark Bruning

03/22/2023, 9:46 PM
Loving Dagster so far, really getting into the Software Defined Assets concept. I have found, however, that when I have a single connection with multiple tables, and those tables are upstream assets of certain DBT source models, for example, I run into problems when trying to materialize the downstream assets. This is because grouped assets in an airbyte connection are not allowed to subset materialization. Is there a good way to allow the materializations trigger for the entire group if one asset needs to be materialized? Or is my only solution to "push down" and materialize the connections and any downstream assets? I really don't want to do that because if I end up having downstream assets from multiple tables in different connections, I'm going to inevitably tie my airbyte materializations together, which is limiting.
b

ben

03/27/2023, 8:44 PM
Hi Mark, right now this is definitely a sore spot with assets which share a compute function & don’t support subselection. Would a new
AssetSelection
parameter be useful here?
e.g.
AssetSelection.groups("my_dbt_group").upstream().required_neighbors()
or something similar?