https://dagster.io/ logo
Join Slack
Powered by
This message was deleted.
# integration-dbt
s
This message was deleted.
s
Hi @Pink Deer - you can override the 
node_info_to_asset_key
argument to 
load_assets_from_dbt_manifest
to provide custom logic for what asset keys to choose for your source assets.
In the future, we're considering making it possible to specify the asset key directly when defining the source
Copy code
version: 2

sources:
  - name: jaffle_shop
    database: raw  
    schema: jaffle_shop  
    tables:
      - name: orders
			  meta:
					dagster_asset_key: jaffle.orders
would this be preferable for you?
j
that yaml you just showed as an example is definitely a preference to me at least
s
here's what the default one looks like:
Copy code
def default_node_info_to_asset_key(node_info: Mapping[str, Any]) -> AssetKey:
    return AssetKey(node_info["unique_id"].split("."))
c
@sandy is this now live with the experimental dbt assets? I saw that we can do it with models as of 0.19.11
s
@rex - are you able to weigh in on this one? I think the answer is yes
r
Yup, this functionality to define the 
asset_key
in the dbt project is out! https://github.com/dagster-io/dagster/releases/tag/1.3.11
c
nice and just want to confirm, this works with sources as well?
r
yup
c
killer
Open in Slack
PreviousNext
Powered by