vmware / vmware/splinterdb

`memtable_try_transition` in `splinter_try_start_incorporate` should be `memtable_transition`

Open
#131 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
732
Forks
67
PR merge metrics
No merged PRs in 30d

Description

The call to memtable_try_transition in splinter_try_start_incorporate should never fail, so this should just be a memtable_transition.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate splinter_try_start_incorporate and inspect its call to memtable_try_transition. Replace that call with memtable_transition, then verify the project still builds and the transition path behaves as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
databases
Issue type
Refactor
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.