remove dependencies on mf_hecke_newspace_traces #6066
Merged
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.
The table
mf_hecke_newspace_traces
takes up a lot of space (about 70GB) and is currently out of date. Extending it to include traces for the new data that has been added (and will be added soon) would increase its size substantially.This table is used to support trace table searches on newspaces (not newforms), but this search is essentially never used --all the examples we could find in the logs were either from us or bots), and I'm not aware of any use case where you would want to identify an entire newspace using traces (without knowing what the newspace is. This PR removes the option for creating trace table search for newspaces from the UI and removes all code dependencies on this table. Once it is merged and pushed to production we can delete
mf_hecke_newspace_traces
.Note that traceforms for each newspace are still shown on newspace home pages and available for download, it is only the ability to search for, e.g. all newpaces with a3=17, that is being removed (supporting this requires a separate row for each individual trace, as well as associated index entries, and this is much more costly than storing an array of traces with each newspace, which we will continue to do).
None of this impacts the ability to do trace table searches on newforms, which we will continue to support.