Proof of concept for a dagsterized approach#290
Draft
jkislin wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This example has dummy assets as a proof of concept; this is not intended to be merged as written, but rather to demonstrate capability and ease of adoption.
@swo @Fuhan-Yang feel free to ignore if not helpful - I know dagster isn't your current priority but figured I'd share this as we start extending to other projects. It was just a few lines of code to tailor existing work (such as what we have in the RTM branch repos) to your repo.
Here's an example asset graph based on these additions:
Note that I'm guessing at what the DAG should look like. A short conversation between us and a small amount of development time should be enough to move this from POC to MVP with feature parity with the
Makefile.