Closed
Bug 1265740
Opened 8 years ago
Closed 8 years ago
Deploy Splice 2.1.8 to stage
Categories
(Content Services Graveyard :: Tiles: Ops, defect)
Content Services Graveyard
Tiles: Ops
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nanj, Assigned: relud)
Details
Please deploy Splice 2.1.8 to tiles stage server. Once Splice gets deployed, there is a script called "expire_redshift_data.py", executing it without any arguments will generate the SQL statements for the data expiry to stdout. By default, the data retention policy for tiles is 13 months. Executing the SQL statements against the stage redshift, it might take some time depends on the size of target tables.
Reporter | ||
Updated•8 years ago
|
Assignee: nobody → dthorn
Assignee | ||
Comment 1•8 years ago
|
||
I think I misunderstood this change. It's really easy for me to write a sql statement that will do that without running a script:
> BEGIN;
> DELETE FROM application_stats_daily WHERE date < (TRUNC(GETDATE())-396);
> DELETE FROM impression_stats_daily WHERE date < (TRUNC(GETDATE())-396);
> DELETE FROM newtab_stats_daily WHERE date < (TRUNC(GETDATE())-396);
> DELETE FROM site_stats_daily WHERE date < (TRUNC(GETDATE())-396);
> COMMIT;
> VACUUM application_stats_daily;
> VACUUM impression_stats_daily;
> VACUUM newtab_stats_daily;
> VACUUM site_stats_daily;
> ANALYZE application_stats_daily;
> ANALYZE impression_stats_daily;
> ANALYZE newtab_stats_daily;
> ANALYZE site_stats_daily;
I thought the script was going to *run* the sql.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•