WIP: Introduce object patcher in client
#248
No reviewers
TrueCloudLab/storage-core-committers
TrueCloudLab/storage-core-developers
TrueCloudLab/storage-services-committers
TrueCloudLab/storage-services-developers
Labels
No labels
P0
P1
P2
P3
good first issue
pool
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-go#248
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/patch_cli"
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?
SplitByMaxChunkLength
methodSplitByMaxChunkLength
method b6b8bdc1628bf00a701b
toc40dbd0810
@ -0,0 +24,4 @@
//
// Must be initialized using Client.ObjectPatchInit, any other
// usage is unsafe.
type ObjectPatcher interface {
What is the purpose of this interface?
Patch
is just another method, similar to PUT.Your point is right - there is no any practical use of this interface right now (like we don't use to mock it in unit-tests and so). However, I was looking through
Put
implementation and came up with idea that client's patcher will need some decoration forpatcher
in the future - so, that was my assumption. If it's really unreasonable, I'll get it awayc40dbd0810
to00547bc32d
Introduce object patcher into WIP: Introduce object patcher inclient
client
Sorry, occaionally created this PR from origin stream branch
ObjectPatch
method #249Pull request closed