Channels
ask-ai
dagster-de
integration-airbyte
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
integration-bigquery
dagster-university
ask-community
dagster-dask
integration-snowflake
dagster-releases
integration-dbt
faq-read-me-before-posting
tools
dagster-insights
dagster-pipes
project-flexible-range-backfills
data-platform-design
community-events
dagster-serverless
dagster-noteable
introductions
integration-airflow
dagster-cloud
random
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
deployment-ecs
deployment-kubernetes
jobs
community-showcase
data-quality-asset-checks
Powered by
#announcements
Title
# announcements
s
schrockn
11/30/2018, 2:10 PM
note: I am leaning towards getting users away from creating ExecutionContexts directly anyways, and instead having them manage loggers and resources instead. but not quite there yet. if we get there though these naming concerns will not matter.
Post