Use GSI Query on Registrations table #415
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
Error removal for adding questions in teams service for dataverse
added for timestamping the submission
Switch Registrations service to using DB query with GSI
Fix Events service dependency on Registrations helpers
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.
Notes
This PR replaces the SCAN operation on the Registrations table being used by the Registrations service and the Events service. We will begin using QUERY to reduce DynamoDB read capacity units (RCU), reduce AWS spend, and reduce latency on the web app.
See #413 and #414 for more details
Testing
Manual testing on dev web app, unit tests