mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Support SELECT ALL semantics for selectors #964
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#964
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roman-khimov on GitHub (Jan 27, 2023).
Is your feature request related to a problem? Please describe.
I'd like to filter out all nodes with some filter and then use all of them in a selector. Looks like there is no way to do that now, I have to specify some count.
This is especially annoying in cases like some on-prem/cloud policy where I'd like to store a copy locally and a copy in a more cloudy environment. I may have a storage node locally, so I'd create a container with
SELECT 1andREP 1. Then I will add a machine to my local environment, but it won't be used for this container.Describe the solution you'd like
It seems like this behavior could be achieved without neofs-api changes, just by some special treatment of
SELECT 0(which doesn't make sense otherwise anyway).Maybe there are other options, let's talk about them here, if
SELECT 0is OK then I'll create an issue in neofs-sdk-go to haveSELECT ALLas another way of writingSELECT 0.