Closed
Bug 884834
Opened 11 years ago
Closed 8 years ago
[database] Missing fields in crashes table
Categories
(Socorro Graveyard :: Bixie, defect)
Socorro Graveyard
Bixie
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: adrian, Unassigned)
References
()
Details
While working on the middleware services for Bixie, I noticed a few problems with the crashes table: - there is no 'version' field in that table - we should not rely on the processed datatime, but on the submitted datetime. I suggest we add a 'submitted_datetime' field that will contain the time when we received the crash, and that we will then be able to use in all our application. The problem with a 'processed_datetime' is that a crash can be re-processed, or it's processing can be delayed, so that is not a consistent value.
Updated•11 years ago
|
Comment 1•11 years ago
|
||
(In reply to Adrian Gaudebert [:adrian] from comment #0) > While working on the middleware services for Bixie, I noticed a few problems > with the crashes table: > > - there is no 'version' field in that table Here are the sample crashes I've seen: https://gist.github.com/lonnen/6f1b364c43f3b21b9138 Where would the version field be pulled from? That key doesn't appear in the sample crash JSON. > - we should not rely on the processed datatime, but on the submitted > datetime. I suggest we add a 'submitted_datetime' field that will contain > the time when we received the crash, and that we will then be able to use in > all our application. The problem with a 'processed_datetime' is that a crash > can be re-processed, or it's processing can be delayed, so that is not a > consistent value. This is for :lars to weigh in on. I'd like for us to be very consistent between bixie and Socorro-core.
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Selena Deckelmann :selenamarie :selena from comment #1) > (In reply to Adrian Gaudebert [:adrian] from comment #0) > > While working on the middleware services for Bixie, I noticed a few problems > > with the crashes table: > > > > - there is no 'version' field in that table > > Here are the sample crashes I've seen: > https://gist.github.com/lonnen/6f1b364c43f3b21b9138 > > Where would the version field be pulled from? That key doesn't appear in the > sample crash JSON. I don't see a 'product' in those sample crashes either, yet we have that field in the crashes table. > > - we should not rely on the processed datatime, but on the submitted > > datetime. I suggest we add a 'submitted_datetime' field that will contain > > the time when we received the crash, and that we will then be able to use in > > all our application. The problem with a 'processed_datetime' is that a crash > > can be re-processed, or it's processing can be delayed, so that is not a > > consistent value. > > This is for :lars to weigh in on. I'd like for us to be very consistent > between bixie and Socorro-core. In Socorro we use 'date_processed', which contains the date when we received the crash, as the reference. We have plans to rename that, see bug 840565.
Comment 3•11 years ago
|
||
From IRC: https://bugzilla.mozilla.org/show_bug.cgi?id=867314 There's a PROJECT_ID in the URL. Let's have the middleware service return data based on project-only for now.
Comment 4•8 years ago
|
||
We're not pursuing Bixie any more.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•8 years ago
|
Product: Socorro → Socorro Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•