529943 - Socorro - materialized view backfilling

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[K Lars Lohn [:lars] [:klohn]]

FF 3.0.15 should have been added to the 'product_visibility' table back on 10/27, but it wasn't.  No aggregates have been accumulated for that p/v as time has passed.  Now we need that data.  How do we get the materialized view code to fill in the missing time period?

Comment 1

[Austin King [:ozten]]

(In reply to comment #0)
If all productdims entries should have a corresponding product_visibility entry, then this is a data migration issue (from when these tables were created).

The following are productdims with no entry in product_visibility on dm-breakpad-stage:
36	Camino	2.0b3	1.9.0	milestone
37	Camino	2.0b2pre	1.9.0	development
38	Camino	2.0b3pre	1.9.0	development
39	Camino	2.0b4pre	1.9.0	development
141	Firefox	3.0.16pre	1.9.0	development
142	Firefox	3.0b4pre	1.9.0	development
144	Firefox	3.5.5pre	1.9.1	development
145	Firefox	3.6b1	1.9.2	milestone
146	Firefox	3.6b2pre	1.9.2	development
108	SeaMonkey	2.0b2	1.9.1	development
109	Firefox	3.0	1.9.0	major
110	Firefox	3.0.1	1.9.0	major
111	Firefox	3.0.2	1.9.0	major
112	Firefox	3.0.2pre	1.9.0	development
113	Firefox	3.0.3	1.9.0	major
114	Firefox	3.0a5	1.9.0	milestone
115	Firefox	3.0a5pre	1.9.0	development
116	Firefox	3.0a6	1.9.0	milestone
117	Firefox	3.0a6pre	1.9.0	development
118	Firefox	3.0a7	1.9.0	milestone
119	Firefox	3.0a7pre	1.9.0	development
120	Firefox	3.0a8	1.9.0	milestone
121	Firefox	3.0a8pre	1.9.0	development
122	Firefox	3.0a9pre	1.9.0	development
123	Firefox	3.0b1	1.9.0	milestone
124	Firefox	3.0b2	1.9.0	milestone
125	Firefox	3.0b2pre	1.9.0	development
126	Firefox	3.0b3	1.9.0	milestone
127	Firefox	3.0b3pre	1.9.0	development
128	Firefox	3.0b4	1.9.0	milestone
129	Firefox	3.0b5	1.9.0	milestone
130	Firefox	3.0b5pre	1.9.0	development
131	Firefox	3.0pre	1.9.0	development
132	Firefox	3.1a1	1.9.1	milestone
133	Firefox	3.1a1pre	1.9.1	development
134	Firefox	3.1b4pre	1.9.1	development
135	Firefox	3.6b1pre	1.9.2	development

Comment 2

[Frank Griswold [:griswolf] [:fgriswold]]

I see no intrinsic reason that every product should have an entry in product_visibilty. Certainly, we have not enforced that in the past.

We could add product_visbility data for each currently unmatched product (with some difficulty if we need to get start,end dates right), but that would leave the system brittle: Adding one more unmatched product/version would once again break things.

More robust: the admin panel should allow product-visibility rows to be added against existing product/version pairs.

Comment 3

[K Lars Lohn [:lars] [:klohn]]

IT Bug 530569 has been submitted to make do the backfill

Comment 4

[K Lars Lohn [:lars] [:klohn]]

This has completed successfully.