[discussion] DB data rotation/partitioning
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
_Friday Oct 09, 2020 at 09:54 GMT_
_Originally opened as https://github.com/facebookincubator/contest/issues/149_
----
This is a follow-up task of discussion: https://github.com/facebookincubator/contest/pull/148
(feel free to edit the issue)
---
# Problem
Currently we just have a database where we store the whole history of anything ever happened. So longer we use ConTest, more data is stored and those tables. And the problem is that in long term any migration/backup/whatever of the DB might take too much time. IMO, it makes sense to consider ways to rotate/archive data or [partition](https://dev.mysql.com/doc/refman/5.7/en/partitioning-types.html) it.
# Action required
So I'm asking to share your thoughts about the problem and possible solutions, including data rotation/archivation and data partitioning. We need to decide what and how we will do about the problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion in pull request 148 and the MySQL partitioning documentation linked in this issue. Compare data rotation, archiving, and partitioning options for the database history, then document a decided approach and its implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100