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
d
Dan Stoner
09/16/2021, 7:50 PMLooking for "how to organize my git repo" help. 'repository' of course being an overloaded concept here. I want to run
dagitworkspace.yamldagit -f hello_dagster.pydagitUserWarning: Error loading repository location repositories.py:dagster.core.errors.DagsterInvalidDefinitionError: Bad return value from repository construction function: all elements of list must be of type PipelineDefinition, PartitionSetDefinition, ScheduleDefinition, or SensorDefinition. Got value of type <class 'module'> at index 0, value of type <class 'module'> at index 1.Maybe I am shooting myself in the foot by trying to use the Experimental APIs. My
hello_dagster.py@pipelinedagit -fdo_it_allHere are contents of `hello_dagster.py`:
from dagster import graph, op
@op
def do_something():
print("Hello Dagster!")
@graph
def do_it_all():
do_something()
if __name__ == "__main__":
do_it_all()Also, just in general... the examples in the doc indicate an awful lot of boilerplate is required... repo.py having to both import every individual thing (pipeline?) and then also return them. I guess this makes everything explicit but somewhat different than "here is my dags folder"
😳 I just found this: https://docs.dagster.io/getting-started/create-new-project which has a repo layout. Will try that.
m
max
09/16/2021, 8:18 PM@prha
p
prha
09/16/2021, 10:18 PM@Dan Stoner yeah, the idea with making it explicit is that you might have different repositories (for different environments) but containing the same graphs. We’re in the process of solidifying a lot of the experimental API support (including docs and the CLI scaffolding).