compaction schedule at database level
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
[NOTE]: # ( ^^ Provide a general summary of the request in the title above. ^^ )
## Summary
[NOTE]: # ( Provide a brief overview of what the new feature is all about. )
## Desired Behaviour
[NOTE]: # ( Tell us how the new feature should work. Be specific. )
[TIP]: # ( Do NOT give us access or passwords to your actual CouchDB! )
## Possible Solution
[NOTE]: # ( Not required. Suggest how to implement the addition or change. )
## Additional context
[TIP]: # ( Why does this feature matter to you? What unique circumstances do you have? )
Contributor guide
Research direction
The issue contains only the title and an unfilled request template, with no files, tests, or entry points identified. Clarify the desired database-level scheduling behavior and acceptance criteria before locating the relevant CouchDB implementation and defining what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100