https://github.com/nspcc-dev/neofs-api/blob/fc8584b766d6b544337fc055dca34c29b0155d31/object/service.proto#L282-L284 was introduced for REP containers. It helps to assemble big objects, for sys needs mostly

Current Behavior

flag is no-op, requested object part is always returned. This is not stated in the protocol

Possible Solution

either:

1. support flag in server implementation
2. mark it no-op in EC protocol, do nothing more

i'm for 2:

• no extra logic
• no need from user side who wants to work with original (root) objects
• no need from sys side, implementation works w/o it

with 2, we may go further and apply the same for REP implementation:

1. support auto-resolution by parent address;
2. deprecate the flag completely

Steps to Reproduce (for bugs)

1. create EC container
2. put object bigger than MaxObjectSize net cfg into it
3. neofs-cli object get --raw

Context

nspcc-dev/neofs-testcases#1222

Regression

no

Your Environment

• Version used: https://github.com/nspcc-dev/neofs-node/releases/tag/v0.50.2