-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ditch Dagster #2523
Comments
A Python package to look into as a possible Dagster replacement: Joblib. |
Joblib looks cool |
The main features of joblib don't look very well aligned with our requirements though (unless I'm missing something). All we need is a system to replace deprecated dagster's PipelineDefinition, SolidDefinition, etc. In other words, we need to be able to (i) define a pipeline (set of jobs where the output of some is the input of some others) and (ii) a function that given a pipeline returns a list of all the jobs that are ready to execute. It should be straightforward to implement and much easier to maintain in the long-run. |
Execution direction was accidentally converted to string in SpineEngine._stop_item() Re spine-tools/Spine-Toolbox#2523
- Replace dagster with jumpster Re spine-tools/Spine-Toolbox#2523
- Use ExecutionDirection enum instead of strings Re spine-tools/Spine-Toolbox#2523
- Fix animations and item icons on Design View and headless mode - Update CHANGELOG Re Issue #2523
This is done. Nice work @manuelma. Dagster is no longer a requirement in 0.8-dev branch. If you plan on hopping between |
Thank you @PekkaSavolainen - to be fair you did most of it. |
As @manuelma puts it in #2522:
We are hooked on an older version, using API that is deprecated in the most recent version. My feeling is we could replicate the bit of functionality that we use from that old dagster with not too much effort (but I might be wrong)?
I have the same feeling. We are not really using much of Dagster's functionality anyway and getting rid of it would fix issues with dependencies and Python versions such as #2522 and #2517
The text was updated successfully, but these errors were encountered: