nspcc-dev / nspcc-dev/neofs-api
"SAME, but different" semantics for selectors
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Suppose I've got 5 DCs and I'd like to have a container that stores 2 replicas in one DC with 2 replicas in another DC. And I don't care which ones it's to choose, just so that they would be different. Looks like this intention can't be expressed with current selectors. I can have a selector using SAME, but if I'm to add another one it could use the same DC as the first one. I can use filters, but that'd make my selection stick to some particular DC.
This may be not the most important use case, but still it's a limitation at the moment.
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
No file, test, or entry point is named. Start by reviewing the selector semantics in the API and proto declarations, then determine how multiple SAME selectors should express distinct, unconstrained data centers. Done means the intended behavior is specified and covered by an appropriate API-level test or example.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100