[Enhancement]: Delete the code related with shared storage
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Enhancement
seekdb does not have shared storage functionality, so the related code can be deleted.
Since the amount of code involved is very large, it needs to be deleted gradually, and a subtask can be created to handle it before deletion. For example, the shared storage code located in ObServerStorageMetaReplayer.
Shared storage code is usually protected using the macro OB_BUILD_SHARED_STORAGE, or determined using the global information GCTX.is_shared_storage_mode.
Contributor guide
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
Start with the shared-storage code in ObServerStorageMetaReplayer and search for the OB_BUILD_SHARED_STORAGE macro and GCTX.is_shared_storage_mode references. Identify one contained subtask and verify the surrounding code remains valid after removing that shared-storage portion. Done means the selected shared-storage code is deleted without leaving broken references.
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
- Mostly clear
- Newbie friendliness
- 35/100