Unistore misses the information needed for plan based RU
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
For PointGet, it doesn't fill the information of `ExecDetailsV2.ScanDetailV2`. As a result, we can't read the `total keys`, `processed keys` and the `processed key size`.
For Scans, its `ExecDetailsV2.ScanDetailV2` is also incomplete。 We cannot read the `total keys` and `processed key size`. In addition, it doesn't fill `ExecDetailsV2.RuV2.CoprocessorResponseBytes` which caused we cannot read the net bytes.
Contributor guide
Research direction
Start by tracing Unistore's PointGet and Scan paths where ExecDetailsV2.ScanDetailV2 and RuV2 are populated. Compare the fields currently reported with the issue's required total keys, processed keys, processed key size, and CoprocessorResponseBytes, then run the relevant execution-detail tests or add coverage showing those values are available for plan-based RU.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100