Channels
dagster-de
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
dagster-bigquery
dagster-support
dagster-dask
dagster-snowflake
dagster-releases
dagster-dbt
faq-read-me-before-posting
tools
dagster-pipes
project-flexible-range-backfills
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-airbyte
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
data-quality-asset-checks
Powered by
#announcements
Title
b
Ben Gotow
12/05/2018, 4:07 PM
yeah - is storing the run ids client side bad? It seemed from the graphQL implementation that the server was keeping all the runs not just the last one, so querying by runID didn’t seem like a problem
Post