Add option to skip splitting rawKV regions when creating new keyspace.
Open
type/enhancement
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 783
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 36
Description
## Enhancement Task
Currently, for every new keyspace created, two sets of region bounds are created to sure different keyspaces' rawKV region and txnKV does not overlap.
But in most scenarios, only txnKV is used, resulting in empty rawKV regions. There should be a option to skip creating rawKV regions when creating new keyspace.
Contributor guide
Assessment
This issue has not been assessed yet.