influxdata / influxdata/influxdb
Retention policy other than duration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Proposal:
Provide retention options based on size or number of records rather than just duration
Current behavior:
Bucket Retention Period
Desired behavior:
"1000 records"
Alternatives considered:
A carry forward query
Use case:
Some use cases are seasonal meaning there is valid data in last duration (Eg 30days) but not if at beginning of season (ie equipment was turned off over winter) where there is no data in a query last 30 days. For storing statistical summaries of datasets that are for last x available, where x is number of records, a retention policy broader than just duration would be helpful.
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
No files, tests, or entry points are identified. Start by reviewing the linked bucket retention-period behavior and determine how record-count or size-based retention should be specified, applied, and validated; completion would require an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100