Memory: Start migrating searchbar JSON out of Educator model #2459
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.
Who is this PR for?
everyone
What problem does this PR fix?
There's a lot of data on the
Educator
model precomputed for the search bar that is otherwise never used when querying the Educator model. This means we're allocating lots of text we never need.What does this PR do?
Starts the migration, adding
EducatorSearchbar
to hold this and updating the controller code to go throughEducatorSearchbar
. Deployment sequence:first:
USE_SEARCHBAR_JSON_ON_EDUCATOR_MODEL=true
USE_SEARCHBAR_JSON_ON_EDUCATOR_MODEL
)next PR (#2460):
as_json
optimizationChecklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?