Tracking: Hash Field Expiration (HFE) implementation
- Dominant language
- C++
- Stars
- 4.4k
- Forks
- 658
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 10
Description
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
### Motivation
Proposal: #3432
This issue is to track the implementation of HFE.
Task list:
- [x] #3444
- [x] #3454
- [x] #3472
- [x] https://github.com/apache/kvrocks/pull/3501
- [x] #3503
- [x] #3506
- [x] #3554
- [ ] Support HFE for replication, slot migration and kvrocks2redis
- ~~Implement a background thread and a dedicated index column family to actively clean up cold expired fields (optional)~~
### Solution
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with proposal #3432 and review the completed task list to understand the existing HFE implementation. The remaining work is to support HFE for replication, slot migration, and kvrocks2redis; done means those integrations work consistently with HFE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, redis
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100