https://dagster.io/ logo
#ask-community
Title
# ask-community
t

Timo

07/21/2022, 12:12 PM
Hi, tags defined on the \@graph level are dropped in later derived graph assets. Is this intended? Worked nice before without any assets and only ops, graphs and jobs.
If I add the tags to the define_asset_job() function, the tags are properly shown in dagit along my job. I think this is a bug/missing feature that the tags are not forwarded.
j

jamie

07/21/2022, 1:28 PM
Hi @Timo i can open a gh issue for this so we can keep track of it
@Dagster Bot issue tags on graph backed assets not forwarded to derived job
d

Dagster Bot

07/21/2022, 1:28 PM
t

Timo

07/21/2022, 1:37 PM
Thanks for creating the issue. To give some more context. We set k8s configs in the tags for the graph. Question: Can we provide kind of hierarchical tags? Meaning: An asset in the job has different tags, and whenever only this single asset is materialized, the tags from the asset are used. If the whole assert_job is executed, the graph/job tags are used?
j

jamie

07/21/2022, 1:43 PM
at the moment, that's not something we support
3 Views