Replace task executor, split workflow #1217
Draft
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.
What's changing
This PR allows a workflow to be specified as a list of jobs to be run sequentially:
Currently, each job will try to use the dataset produced by the previous job (if any), and the workflow will merge all results together in a single result. Tasks are handled using asyncio Tasks and stored in a dict within their appropriate service (jobs or workflows) using their created ID as a key. The dict should do auto cleanup when the Task completes.
It currently needs support from the UI to be used there, but auto tests should work ok.
Closes #774
How to test it
Run the auto tests and follow the job information in Ray and MLFlow. Everything should be stored in their place.
Additional notes for reviewers
N/A
I already...
/docs
)