Support SELECT ALL semantics for selectors #964

Open
opened 2025-12-28 17:21:19 +00:00 by sami · 0 comments
Owner

Originally created by @roman-khimov on GitHub (Jan 27, 2023).

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 1 and REP 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 0 is OK then I'll create an issue in neofs-sdk-go to have SELECT ALL as another way of writing SELECT 0.

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 1` and `REP 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 0` is OK then I'll create an issue in neofs-sdk-go to have `SELECT ALL` as another way of writing `SELECT 0`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#964
No description provided.