https://dagster.io/ logo
Powered by
c

Chris Evans

10/05/2021, 8:55 PM
Is it still possible to select a subset of a graph/job to execute in the Dagit playground when using the new API paradigm? If so I see two unexpected behaviors in 
0.12.11
. Firstly, Dagit seems to detect errors around missing config for ops that are deselected. Secondly, even if a subset of a graph is selected in the Dagit playground, all ops will end up running when execution is launched.
Copy code
from dagster import graph, op


@op(config_schema={"param": str})
def hello(context):
    ...

@op(config_schema={"param": str})
def hello2(context):
    ...

@graph
def test_graph():
    hello()
    hello2()


test_job = test_graph.to_job()
p

prha

10/05/2021, 9:02 PM
cc @yuhan
y

yuhan

10/05/2021, 9:08 PM
Hi @Chris Evans, Dagit at the moment doesn’t support subsetting a graph/job in the playground. I’m working on it.
c

Chris Evans

10/05/2021, 9:11 PM
Good to know! Thanks @yuhan
Perhaps of the same vein… I found the behavior in Dagit odd as well in the new paradigm w/ partition sets/config maps i.e. abstractions w/ dynamic config. I am only able to see the dynamic config params in the Dagit playground not any of the other supplied config.
y

yuhan

10/05/2021, 9:24 PM
i believe so. cc @chris for config mapping on graphs
4 Views
Powered by