nspcc-dev / nspcc-dev/neofs-api
Weak replicas
Open
Nobody has claimed this yet.
enhancement
I3
S3
U4
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when we can't declare weak replication policy when an object can be placed to some group of nodes, but can leave it at the same time. This can be useful for caching.
Describe the solution you'd like
Add "weak" parameter to replication rule.
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 by locating the replication rule declaration in the repository's proto files and read how existing replication policies are represented. Clarify the intended semantics of a weak policy, then define the API change so a replication rule can express it and verify that the updated declaration is consistent with the surrounding API.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100