[DEV-11465] Change spending_by_geography to use Elasticsearch for Subawards #4290
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
…api into mod/dev-11465-spending-by-geo-subawards-on-es
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.
Description:
Updating the
/search/spending_by_geographyendpoint to use Elasticsearch instead of Postgres.Technical details:
Changes involve a lot of cleanup of the old Django ORM code and cutting over the Subaward logic to use Elasticsearch. Other changes include many updates to tests so that the Subawards are loaded correctly into Elasticsearch and a minor change to how the New Awards Only logic was previously setup to work when searching for Awards.
Requirements for PR merge:
Area for explaining above N/A when needed: