Closed
Bug 517952
Opened 15 years ago
Closed 15 years ago
Download statistics are zero for 2009-08-31 and 2009-09-01
Categories
(addons.mozilla.org Graveyard :: Statistics, defect)
addons.mozilla.org Graveyard
Statistics
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: smccammon, Assigned: smccammon)
References
()
Details
Attachments
(2 files)
796 bytes,
patch
|
clouserw
:
review+
|
Details | Diff | Splinter Review |
737.62 KB,
image/png
|
Details |
Supposedly the global_stats maintenance script failed on these two days, and the counts have been 0 ever since. Note that the 0 count days are 1 day off if you go by the timeplot hover values (see bug 514543).
Running the following SQL should rectify the situation and remove the hole from the downloads graph:
REPLACE INTO global_stats (name, count, date) VALUES ('addon_downloads_new', (SELECT IFNULL(SUM(count), 0) FROM download_counts WHERE date = '2009-08-31'), '2009-08-31');
REPLACE INTO global_stats (name, count, date) VALUES ('addon_downloads_new', (SELECT IFNULL(SUM(count), 0) FROM download_counts WHERE date = '2009-09-01'), '2009-09-01');
Comment 1•15 years ago
|
||
If you create a migration with this in it (just pick a revision and then add a comment that says it has nothing to do with that) it'll get picked up when we push.
Assignee | ||
Comment 2•15 years ago
|
||
A fine suggestion by clouserw: here is a db migration that should fill in the holes.
Assignee: nobody → smccammon
Attachment #401922 -
Flags: review?(clouserw)
Updated•15 years ago
|
Attachment #401922 -
Flags: review?(clouserw) → review+
Assignee | ||
Comment 3•15 years ago
|
||
Fixed in r52042.
Preview metrics data seems to be outdated, so this probably can't be verified until the 5.1 push to production.
Comment 4•15 years ago
|
||
Comment 5•15 years ago
|
||
Verified FIXED on https://addons.mozilla.org/en-US/firefox/statistics/
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Keywords: push-needed
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•