Bug 1762000 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

In bug #1393416, we removed the processor rule that copied the `Winsock_LSP` value from the raw crash to the processed crash. The thinking was that no one searches with this field, so we didn't want it in Elasticsearch and if we weren't using it in Elasticsearch, we didn't need to copy it in the first place.

Cool. So we removed the processor rule, but we didn't remove the entry from `super_search_fields.py` `FIELDS` and the field gets populated from `processed_crash.Winsock_LSP`. So this field in Elasticsearch is always empty.

Further, there's an entry in `telemetry_socorro_crash.json` schema. That data will never get populated because there's nothing in the processed crash.

Given that this field has been empty in `telemetry.socorro_crash` and Elasticsearch since 2019, I'm going to assume that's fine so I'm going to remove it from everything.
In bug #1393416, we removed the processor rule that copied the `Winsock_LSP` value from the raw crash to the processed crash. The thinking was that no one searches with this field, so we didn't want it in Elasticsearch and if we weren't using it in Elasticsearch, we didn't need to copy it in the first place.

Cool. So we removed the processor rule, but we didn't remove the entry from `super_search_fields.py` `FIELDS` and the field gets populated from `processed_crash.Winsock_LSP`. So this field in Elasticsearch is always empty.

Further, there's an entry in `telemetry_socorro_crash.json` schema. That data will never get populated because there's nothing in the processed crash.

Given that this field has been empty in `telemetry.socorro_crash` and Elasticsearch since 2019, I'm going to assume that's fine so I'm going to remove it from Elasticsearch and mark it as empty and deprecated in `telemetry_socorro_crash.json`.

Back to Bug 1762000 Comment 0