🏗️ Make ETL pipeline async #13
Draft
Conversation
This file contains 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.
Summary
The aim of this PR is to move away from the current batch ETL workflow for creating pluto reports, to be replaced with an asynchronous workflow.
Details
The current workflow extracts data from APIs in batch, then cleans up and applies preliminary statistics and filtering on it in batch, and finally loads all data to the
*.gzipfiles in batch.This makes the workflow very unstable to unexpected API behaviour and other failures due to data inconsistencies.
Thus to make the workflow more robust to these potential issues, and reduce memory usage in report generation, This PR changes the architecture to the one described above.
Key
Gray lines are initiated by the pluto report generating user.
Blue lines are initiated by the book report generator/refresher.