Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement operational database purging #489

Merged
merged 9 commits into from
Jan 17, 2024
Merged

Implement operational database purging #489

merged 9 commits into from
Jan 17, 2024

Conversation

spbnick
Copy link
Collaborator

@spbnick spbnick commented Jan 16, 2024

Add a cloud function and a cloud scheduler job for purging the operational database of data that is older than six months, rounded down to month boundary.

Introduce the concepts of "operational database" and "archive database".

The "operational database" is the one where most operations are done,
and which has recent data only, as opposed to "archive database", which
keeps all the data, but is either slow or expensive to query. In our
case the former is PostgreSQL and the latter is BigQuery.

Export the operational database specification to Cloud Functions as
"KCIDB_OPERATIONAL_DATABASE", and the archive database as
"KCIDB_ARCHIVE_DATABASE".
Add a cloud function and a cloud scheduler job for purging the
operational database of data that is older than six months, rounded down
to month boundary.
@spbnick spbnick force-pushed the support_op_db_purging branch from 3f95401 to 5d3df49 Compare January 17, 2024 07:35
@spbnick spbnick merged commit 2b390c3 into main Jan 17, 2024
5 checks passed
@spbnick spbnick deleted the support_op_db_purging branch January 17, 2024 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant