tyzbit / tyzbit/acars-processor
SQLite Message Culling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When using the databases, messages are marked as deleted but are not actually deleted. This can take up a lot of space quickly and can adversely affect performance.
We can implement message culling such that the database is cleaned up according to number of messages, date of oldest message or cull as soon as a message is processed to use the database solely as a persistent message queue.
Contributor guide
No contributing guide indexed for this repository
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
No source files or tests are named. Start by locating the SQLite message-processing and deletion code, then clarify whether culling is based on message count, oldest-message date, or processing completion. Done should include a defined culling policy and verification that processed messages are removed without breaking the persistent queue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100