Extend PatchRequest.Body
with new_split_header
field #81
Labels
No labels
P0
P1
P2
P3
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api#81
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-api:fix/patch_split"
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?
FYI: we can't generate docs with
edition=2023
directivePatchRequest.Body
withnew_split_header
field3a34a886f0
tod0f583220b
@ -889,1 +889,4 @@
// New split header for the object. This defines how the object will relate
// to other objects in a split operation.
neo.fs.v2.object.Header.Split new_split_header = 5;
Do we decided add only split header, not any other system attributes?
True, but I have changed my mind:
ContainerID
andOwnerID
, then the result will be unpredictable (or it'll be a huge disaster)split_header
is enough and no other system attribute is required to get patched. Initially my concern was to take into account all necessary fieldsThe same thing was being said about splitheader some time ago :)
I don't mind adding this field explicitly, but we need to be sure that it is enough for the usecase we are trying to support.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.