https://dagster.io/ logo
Title
a

Andreas Fred Ojala

11/17/2022, 12:39 PM
Hello everyone. I have two assets with configuration possible. If I try to materialize one of the assets (from the asset page) I need to put in the config for the other asset as well. Is there a way to mitigate this (apart from creating a job for each asset)? Minimal reproducible code in the comments and a screenshot
from dagster import (
    asset,
    repository,
    OpExecutionContext,
)


@asset
def upstream_asset():
    return 1


@asset(config_schema={"test": int})
def downstream_asset(context: OpExecutionContext, upstream_asset):
    return upstream_asset + context.op_config["test"]


@asset(config_schema={"input": int})
def standalone_asset():
    return 0


@repository
def repo():
    return [upstream_asset, downstream_asset, standalone_asset]
s

sandy

11/17/2022, 3:58 PM
@sean @Ben Gotow - is this expected behavior?
s

sean

11/17/2022, 4:01 PM
I’m loading up the sample code now, let’s see
no, this is a bug. Thanks for the report @Andreas Fred Ojala.
@Dagster Bot issue Fix unnecessarily required config when materializing asset subset
d

Dagster Bot

11/17/2022, 4:10 PM
a

Andreas Fred Ojala

11/18/2022, 6:57 AM
No worries, thanks for the support!