Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix/complex objects relations #2810

Merged
merged 8 commits into from
Apr 17, 2024
Merged

Fix/complex objects relations #2810

merged 8 commits into from
Apr 17, 2024

Commits on Apr 16, 2024

  1. policer: Store link objects on every container node 

    It will simplify inhuming children objects without network communications.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 16, 2024
    Configuration menu
    Copy the full SHA
    1eda24a View commit details
    Browse the repository at this point in the history

  2. shard: Allow setting targets without changing the original operation 

    Can be used for internal root objects extension (when inhuming the root object
should become inhuming all the children operation). Also make all the setters
check nil pointers to be in sync.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 16, 2024
    Configuration menu
    Copy the full SHA
    c5351d7 View commit details
    Browse the repository at this point in the history

  3. engine: Support inhuming parts by root object ID 

    We are moving towards not using child objects in the helpers objects
(Tombstones and Storage groups) so engine should learn to live with it first.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 16, 2024
    Configuration menu
    Copy the full SHA
    26704f9 View commit details
    Browse the repository at this point in the history

  4. engine: Drop useless checkExistsparameter for inhumeAddr 

    Now we are always checking if objects exists.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 16, 2024
    Configuration menu
    Copy the full SHA
    3e005a0 View commit details
    Browse the repository at this point in the history

  5. core/object: Drop confusing comment 

    This part of the code does not mark anything.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 16, 2024
    Configuration menu
    Copy the full SHA
    56d629e View commit details
    Browse the repository at this point in the history

Commits on Apr 17, 2024

  1. node/object: Do verify tombstone's members 

    Do not allow putting tombstones that contain any child object of a complete
(finished, fully uploaded) user's big object. Only unfinished big objects can be
partially put to a tombstone to perform garbage collecting.
From now, client should attach only root object IDs to the tombstones, all the
removal magic will be applied later internally.
Closes #2093.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    b670d75 View commit details
    Browse the repository at this point in the history

  2. node/delete: Do not collect child objects for tombstones 

    It is prohibited and validated now.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    d0a1f4c View commit details
    Browse the repository at this point in the history

  3. neofs-cli/object/delete: Do not collect object relatives 

    They are not required, only root objects can be placed to a tombstone.

Signed-off-by: Pavel Karpy <[email protected]>
    @carpawell
    carpawell committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    e97444a View commit details
    Browse the repository at this point in the history