User Details
- User Since
- Jan 19 2021, 6:42 PM (123 w, 3 d)
- Roles
- Disabled
Aug 17 2021
Aug 9 2021
makes sense -- I only kept it around in case we ended up using it for something, but I suppose git history will do.
Aug 4 2021
totally agree with getting rid of this -- it'll also make the dogfooding alert channel much less annoying :)
Aug 2 2021
Like the general shape of this + how it makes the interface feel more similar to @op
Jul 30 2021
Jul 29 2021
@sandyryza Writing out / formalizing some stuff from our conversation yesterday, it feels like there are two distinct cases where a person might want to include things that don't produce "assets" (long-living objects external to the dagster ecosystem) within their asset oriented pipeline.
Jul 28 2021
Jul 27 2021
Jul 26 2021
Jul 23 2021
Jul 21 2021
not sure what the deal is with pokemon in reviews but when in rome...
Jul 20 2021
Jul 19 2021
Jul 16 2021
Jul 14 2021
Nice -- one step closer to banishing solids from this world
Jul 13 2021
Jul 12 2021
one other option that might work would be to remove the PROFILES_DIR configuration (https://sourcegraph.com/github.com/dagster-io/dagster/-/blob/examples/dbt_example/dbt_example/solids.py?L11). It seems like the value that it's set to is the default value for dbt, so it doesn't really do anything, and might be having some weird interaction with the update. The changelog for dbt mentions some changes to how they interpret the profiles-dir path (relative to the project-dir path vs absolute) that I wouldn't think would impact us, but it seems possible that this would be a buggy side effect
Jul 6 2021
- add extra explanation
- rebase
- rebase
- Updated docs for dbt integration
Jul 1 2021
- up
- rebase
- major refactor
- make black
- major refactor
Jun 25 2021
Jun 16 2021
Overall, I like this direction, but I do think there are many cases where you might want to depend on multiple asset keys at once (the story_recommender pipeline is one example). This does add bits of complexity basically everywhere (need a fancier cursor object, and it's not obvious what exactly should be passed into the user's sensor function when just a single one of the many asset dependencies has been updated), but I do think that people will look for this functionality pretty quickly, and it would be nice to have a good story for them..
rebase
Jun 10 2021
Jun 9 2021
- changed ParquetPointer to NamedTuple
- added some explanations
- added some explanations
Jun 8 2021
up
rebase
up
up
Overall, I like the guide, but I think we can simplify it a little bit.
Jun 7 2021
added some tests for weird things people might do with generators and solids
Jun 4 2021
up
up
up
I always did wonder why it was called environment in this context 🤔
up
up