Return OID if an object was PUT but num of REPs is not enough (but > 0) #1445

Closed
opened 2025-12-28 17:23:01 +00:00 by sami · 2 comments
Owner

Originally created by @carpawell on GitHub (Jun 27, 2025).

I'm always frustrated when incomplete object put err cannot be "undone" or be treated as OK.

Describe the solution you'd like

If i see incomplete PUT, i should see its ID if at least one node stores the object. Otherwise, this object is kinda lost. If OID was calculated and there is at least one successful object PUT, return the object ID, but still say it is an error.

Describe alternatives you've considered

Keep as is.

Originally created by @carpawell on GitHub (Jun 27, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when incomplete object put err cannot be "undone" or be treated as OK. ## Describe the solution you'd like If i see incomplete PUT, i should see its ID if at least one node stores the object. Otherwise, this object is kinda lost. If OID was calculated and there is at least one successful object PUT, return the object ID, but still say it is an error. ## Describe alternatives you've considered Keep as is.
sami 2025-12-28 17:23:01 +00:00
Author
Owner

@carpawell commented on GitHub (Jun 27, 2025):

Maybe incomplete err should be a separate status then.

@carpawell commented on GitHub (Jun 27, 2025): Maybe incomplete err should be a separate status then.
Author
Owner

@roman-khimov commented on GitHub (Sep 23, 2025):

Related to https://github.com/nspcc-dev/neofs-api/pull/346

@roman-khimov commented on GitHub (Sep 23, 2025): Related to https://github.com/nspcc-dev/neofs-api/pull/346
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#1445
No description provided.