pool: Add copies number vector when putting object #57
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-go#57
Loading…
Reference in a new issue
No description provided.
Delete branch "ironbee/frostfs-sdk-go:add_copies_number_vector"
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?
Closes: #44
Signed-off-by: Artem Tataurov a.tataurov@yadro.com
@ -1259,2 +1263,3 @@
copiesNumber uint32
copiesNumber uint32
copiesNumberVector []uint32
Actually, we can preserve only
copiesNumberVector
and make the follwoing changesAlso we should add new method to set vector:
@ -615,7 +615,11 @@ func (c *clientWrapper) objectPut(ctx context.Context, prm PrmObjectPut) (oid.ID
}
var cliPrm sdkClient.PrmObjectPutInit
cliPrm.SetCopiesNumber(prm.copiesNumber) // TODO(@ironbee): adopt multiple copy number https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go/issues/44
With this we can just write:
8f8022313b
to8611eaaeae
@ -1276,0 +1277,4 @@
}
// SetCopiesNumberVector sets number of object copies that is enough to consider put successful, provided as array.
// Zero means using default behavior.
We cannot provide "zero", so probably we can drop this comment line
Well, I would say that it could be rephrased to "Nil/empty vector means using default behavior.", it describes the lie of the land better than nothing at all
8611eaaeae
to1ce41bf85f
1ce41bf85f
to767a6a7d51
767a6a7d51
to787be46c58
787be46c58
tod0762d037d