Refactor the management of rocksdb ColumnFamily
- 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
Currently, kvrocks has multiple Column Families, and some configs are written ad-hoc. So, some issues below would be tricky:
1. https://github.com/apache/kvrocks/issues/2193
2. https://github.com/apache/kvrocks/issues/2263
Now I think we need a class for owning the kvrocks cf configs.
### Solution
A unified CF manager
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how kvrocks currently defines and manages its RocksDB Column Families and ad-hoc configs, then review issues 2193 and 2263 for the problems this refactor should address. Done means the Column Family configurations are owned through one unified manager.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100