What I mean particularly is that some of the alternatives do

Question

What I mean particularly is that some of the alternatives don t seem to link up These assets are partitioned on a static list of values and as best I can tell from the docs the only way to set up a partitioned asset is via the `partitions def` argument to the ` asset` decorator If I want to add metadata to a materialisation the docs only mention how to do it via an `op` based asset or from a custom IO manager So I could make them an `op` in a graph backed asset maybe But I can t see any docs on how to partition graph backed assets I know you can actually because I went digging in the source for `AssetsDefinition from graph ` but it s not at all clear from the docs

Stephen Bailey · Answer

I know that one way you can log metadata is via the `context add output metadata` method which will log whatever is in the dict to the AssetMaterialization event that running the asset produces I m not sure how this plays with partitions yet

Stephen Bailey · Answer

``` asset def my asset context context add output metadata how cool so cool return 1 2 3 ```

Stephen Bailey · Answer

Also my understanding is that all assets are op backed assets Under the hood asset is basically an op with superpowers

claire · Answer

Hi Ben In addition to what Stephen mentioned you can also add metadata to an asset materialization by doing something like this ```yield Output 5 metadata= my metadata 5 ```

claire · Answer

I can file a ticket to document partitioning graph backed assets

claire · Answer

< Dagster Bot> docs no documentation for partitioned graph backed assets

Dagster Bot · Answer

Created issue at <https github com dagster io dagster issues 9281>

claire · Answer

< Dagster Bot> docs missing documentation for attaching metadata to asset materialization

Dagster Bot · Answer

Created issue at <https github com dagster io dagster issues 9282>

Ben Gatewood · Answer

Thanks Stephen and Claire To be clear I don t think any actual functionality is missing here but I found myself chasing my tail a bit through the docs on this one

claire · Answer

Definitely thanks Ben for reporting these gaps Docs improvements are important to us and we definitely want to improve our coverage Please feel free to report future questions docs issues

Ben Gatewood · Answer

Yup will do Overall I think they re already really good btw I don t normally have to spend very much time in there to find what I need