clean up super search fields from migration [August 2022]
Categories
(Socorro :: Processor, task, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
References
Details
Attachments
(1 file)
In bug #1753521, we stopped indexing things from the raw crash. In bug #1755528, we unified all the boolean data. In bug #1762005, we migrated some fields to snake_case names.
For all of these, because we want to do them seamlessly, we're doing them in two steps. Step 1 is to set things up so we're indexing the data in two places: the current place that's used for super search and the future place we're going to use for super search. That lets super search continue to work while we accumulate data in the new field.
This bug covers the second step where we remove the old fields and everything related to them so we're only indexing into the new field. We shouldn't do it any earlier than August 2022.
|
Assignee | |
Comment 1•2 years ago
|
||
I'm doing this now because I have a little bit of time and we can't do a prod deploy for a week or two.
|
|
Assignee | |
Comment 2•2 years ago
|
||
|
|
Assignee | |
Comment 3•2 years ago
|
||
willkg merged PR #6126: "bug 1763264: finish super search migration" in ae60bf4.
We should wait for this to deploy to stage and then for a new Elasticsearch index to be created to make sure it doesn't kick up errors before we push this to prod.
|
|
Assignee | |
Comment 4•2 years ago
|
||
I deployed this in bug #1782791 just now. Marking as FIXED.
Description
•