Closed
Bug 934498
Opened 12 years ago
Closed 8 years ago
Add "collector notes" field to record information about collector actions taken on raw crashes
Categories
(Socorro :: Backend, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: selenamarie, Unassigned)
References
Details
From lars:
I suggest that we add a new field to the raw_crash called 'collector_notes' similar to the processed_crash's 'processor_notes'. The logging of problems and what actions were taken should happen in that 'collector_notes' key so that the information is carried along with the raw_crash and can be acted on or displayed later down the processing pipeline.
Comment 1•8 years ago
|
||
Mmmm... If I had my druthers, the collector wouldn't be changing the raw crash at all. Once we change the raw crash, forever it is changed and unless we keep the old and new values, we no longer have the original crash form.
If I had my druthers, I'd move de-nulling and any other transformations to the processor. Then if there are bugs or other oddities that we discover in the de-nulling, we can fix them and reprocess from the original raw crash.
I opened bug #1357246 to cover moving the de-nulling code to the processor that already has a notes field.
Given that, I'm going to close this out.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•