Make WAL transactions file limited
Open
Nobody has claimed this yet.
New feature
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
Is your feature request related to a problem?
WAL transaction file _txnlog grows with every commit.
Describe the solution you'd like.
There should be a way to automatically trim its historical records.
Describe alternatives you've considered.
No response
Full Name:
Alex Peagenko
Affiliation:
QuestDB
Additional context
No response
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 locating the WAL transaction log implementation and examining how _txnlog records are written and retained. The issue is complete when historical records are automatically trimmed so the transaction file remains bounded, with the retention behavior defined and verified by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100