19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
c
Chris Evans
10/05/2021, 8:55 PMIs 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.11from 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 PMcc @yuhan
y
yuhan
10/05/2021, 9:08 PMHi @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 PMGood 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 PMi believe so. cc @chris for config mapping on graphs