Stub Out ETL Endpoint #9
Merged
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
swellander
approved these changes
Jun 16, 2024
There was a problem hiding this comment.
@escottalexander sorry for the late review! The endpoint you stubbed out looks good 👍 and thanks for including the descriptions of the different impact metrics we'll be using
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.
OSO will provide timestamped data for querying so we don't need to think about storing the actual data on a daily basis. But since the data does need a little processing (applying the weights, aggregating to get totals) it makes sense to keep this structure to ensure the end user does the minimal amount of data processing to see it on their front end.
Closes #8