Closed Bug 722936 Opened 14 years ago Closed 14 years ago

Create database infrastructure for correlations reports

Categories

(Socorro :: Database, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jberkus, Assigned: jberkus)

References

Details

(Whiteboard: [qa-])

Spinning this off into its own bug so that we can resolve it. In order to support in-socorro correlation reports, we need: 1. tables to hold all correlation listings 2. matview population functions for: 2.1. correlation index (signature, product, reason) 2.2. addon correlations 2.3. arch/cores correlations (1) is already written, checked in, and installed on DevDB. (2) is not currently written.
Backfill procedures written and landed on crash-stats-dev, but not bug-free. So, having a couple interesting issues with this: (1) due to more Frank-enstein insanity, the Extensions and Plugins tables in the database do NOT contain copies of the UUID, but only rather the report_id, an extra, unnecessary, serial key not related to the UUID. This is preventing the fill-in of correlations_extensions, and I will need to do a bizarre dosey-doh with ID mapping to fix it. Darn you, Griswolf! (2) Per spec, the update_correlations always runs for yesterday. This works fine for prod, but on dev this means that the table is constantly getting blanked out, since dev falls behind. Ideas?
mass migration of correlation-report related bugs that won't land today.
Target Milestone: 2.4.2 → 2.4.3
Even though this has been postponed to 2.4.3, the database underpinnings are done, tested and landed on crash-stats-dev. So marking them as resolved.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.