Closed Bug 1762000 Opened 11 months ago Closed 10 months ago

fix Winsock_LSP situation

Categories

(Socorro :: Processor, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

Attachments

(1 file)

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.

Assignee: nobody → willkg
Status: NEW → ASSIGNED
URL: 1393416
See Also: → 1393416

This went to production in bug #1763234. Marking as FIXED.

Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.