Refine MVCC Write
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- C++
- Stars
- 41
- Forks
- 56
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Currently, the MVCC Write is only used by test, some features is yet to add, like rollback asyncly after write fails. Maybe we'd better maintain serveral rollback queues rather than per rollback per thread.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests. Start by locating the MVCC Write implementation and its existing tests, then clarify the failure-rollback behavior and whether rollback queues should be shared or per thread before defining what a complete change entails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100