Closed
Bug 1105555
Opened 10 years ago
Closed 10 years ago
New migrations for temporary 'compression' tables
Categories
(Content Services Graveyard :: Tiles: Administration Front-End, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Iteration:
36.3
People
(Reporter: Mardak, Assigned: tspurway)
References
Details
(Whiteboard: .007)
Copied from https://github.com/oyiptong/splice/issues/38
Each day we are going to compress the previous day's data in impression_stats_daily and newtab_stats_daily. We need a temporary table to hold data for this process to work. These should be implemented as migrations.
Assignee | ||
Comment 1•10 years ago
|
||
We expanded the size of our Redshift cluster, and so this issue has been (perhaps temporarily) relieved. Our queries are very fast, and I have decreased the frequency of Redshift inserts, which will have the effect of reducing the growth rate.
Reporter | ||
Comment 2•10 years ago
|
||
Per comment 1, sounds like we don't need to do this for now but might be something to do if the situation arises later. Resolving INVALID for now (as opposed to WONTFIX).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Reporter | ||
Updated•10 years ago
|
Whiteboard: .? → .007
Reporter | ||
Comment 3•10 years ago
|
||
Looks like this was fixed
https://github.com/oyiptong/splice/pull/39
Resolution: INVALID → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•