would like to understand 1) when do I use Table and 2) its value.
Fri, Jul 10
Wed, Jul 8
Tue, Jul 7
Mon, Jul 6
this is awesome!! thanks for doing it! it looks great but i will let sashank take the last pass.
@schrockn I see dagster-test as a place to put all the code shared by many python modules so we don't need to replicate test snippets or use code in examples/.
integration tests wise, i dont have strong opinions on where to put, but slightly prefer to have it separate from dagster-test and just keep dagster-test a simple "shared examples used by tests"
Thu, Jul 2
delete unused file
Wed, Jul 1
once you land it, can you update this accordingly? https://github.com/dagster-io/dagster-docs/blob/master/netlify.toml
Looks good overall
Tue, Jun 30
I actually slightly prefer to keep the readmes with the example code in examples/, because it feels natural when someone opens dagster repo and browser examples on github, they could just read through github without going anywhere else, like this link https://github.com/dagster-io/dagster/tree/0.8.5/examples/basic_pyspark
Fri, Jun 26
Thu, Jun 25
Wed, Jun 24
Tue, Jun 23
@sandyryza how do you feel about having a long glossary page (e.g. https://databricks.com/glossary) but divided by section like modes, resources, logging, etc, and then link the section on the bottom of each overview page?
Mon, Jun 22
I'm fine with pandas, because I wouldn't expect people to follow/copypaste/run the intro code -- even just a few func names with pass would be fine IMO.
But I think we could have a better example to demonstrate our values: easy to organize pipeline code (elegant programming model), UI, programmatic APIs.
Sat, Jun 20
Fri, Jun 19
Thu, Jun 18
Wed, Jun 17
in D3221 i renamed PipelineDefinition.subset_for_execution(solid_subset) to PipelineDefinition.get_pipeline_subset_def(solids_to_execute), because previously both ExecutablePipeline and PipelineDefinition have a func called subset_for_execution so i did the renaming to avoid confusing.
it may be worth reading the summary sections in D3221 and D3225 to get the context of the subsetting refactor we did after this diff