migrate to lower-cased versions of Plugin* fields in processed crash
Categories
(Socorro :: Processor, task, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
References
Details
Attachments
(1 file)
The processor has a PluginRule that copies several fields from the raw crash to the processed crash. Then Elasticsearch has several plugin_* fields that look at the processed crash for data and saves them as snake case versions of those names. Further, the telemetry crashstorage looks for snake case versions of those names.
Given we're converting to snake case versions of the names in multiple places, we should change the processor rule to save with the snake case names.
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Comment 1•3 years ago
|
||
We do have some plugin data. I have no idea if it's searched for. I'm going to implement this as a migration and we'll do the second step in 4+ months.
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
|
Assignee | |
Comment 3•3 years ago
|
||
willkg merged PR #6048: "bug 1762005: change Plugin* to snake_case" in 7b65cc4.
I need to make sure the changes here in Elasticsearch super_search_fields.py work across index boundaries, so we'll need to wait until next week and test out searching with plugin_name.
|
|
Assignee | |
Comment 4•3 years ago
|
||
Everything so far went to production in bug #1763234 just now. Followup work will be done in bug #1763264. Keeping this open to verify everything is working on Monday after we've created a new Elasticsearch index.
|
|
Assignee | |
Comment 5•2 years ago
|
||
I verified that I can search for plugin_name across indexes, so I think we're good here. Marking as FIXED.
Description
•