The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

maybe via a config param or something so we can turn it on and destroy things

<@UCMSYKG1Y> <https://github.com/dagster-io/dagster/pull/359>

<@UCMSYKG1Y> <https://github.com/dagster-io/dagster/tree/log-spew/python_modules/dagster/dagster/dagster_examples/log_spew>

`dagster pipeline execute -f pipeline.py -n define_spew_pipeline -e env.yml`

you can turn the verbosity up or down by modifying the env.yml

this is great - lemme pull it down and try it in a min

hey gang I put up a PR with the execution plan improvements - <https://github.com/dagster-io/dagster/pull/360>. also put in the “click red dot to see pythonError” thing we talked about <@UCCLPK5G8>

PUpqokK.jpg

<@UEMUH5H4H> welcome to the dynamic language lifestyle ^^^

from the dbt slack: ```dbters: do you ever get the request to have a materialization option for a table that drops the table after the pipeline finishes? I’ve used this pattern a lot in the past for performance reasons. You run a pipeline and instead of using ctes, sometimes you need either a materialized view or a temp table to keep performance of transformations humming along. (classic example is when cross joins are involved in a temp table creation, but you don’t want the table hanging around after you use it).```

oh lol, that comment is from ben castleton

<@UCFFSJ3EX> he’s a superconductive employeee

fucking toy editors, pasting api mocks in my editor kills it

<@UCFFSJ3EX> be careful merging other’s branches. that PR you merged was actually based off another feature branch of mine.

caught it but that could have gotten confusing again

ok, please mark this in title and/or description 

the Dict thing is a huge usability improvement

the turnaround is very slow with remote if we assume branches are unmergeable

i should have marked it; and we should move to phabriactor