[#237] pool: Return creation epoch from object put #237
No reviewers
TrueCloudLab/storage-sdk-developers
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
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-go#237
Loading…
Reference in a new issue
No description provided.
Delete branch "mbiryukova/frostfs-sdk-go:feature/epoch_from_object_put"
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?
Signed-off-by: Marina Biryukova m.biryukova@yadro.com
8d764f37aa
to0858160c88
[#xxx] pool: Return creation epoch from object putto [#237] pool: Return creation epoch from object put@ -80,6 +81,10 @@ func (x ResObjectPut) StoredObjectID() oid.ID {
return x.obj
}
func (x ResObjectPut) StoredEpoch() uint64 {
We need comment I suppose (to be consistent with other methods)
@ -96,0 +97,4 @@
epoch uint64
}
func (r *ResObjectPutSingle) Epoch() uint64 {
Also need comment
@ -2449,3 +2449,3 @@
//
// Main return value MUST NOT be processed on an erroneous return.
func (p *Pool) PutObject(ctx context.Context, prm PrmObjectPut) (oid.ID, error) {
func (p *Pool) PutObject(ctx context.Context, prm PrmObjectPut) (oid.ID, uint64, error) {
Let's introduce new struct that contains both id and epoch rather than return these values individually
0858160c88
to249f76cfe8
OK with me
@ -2460,2 +2472,3 @@
var ctxCall callContext
var (
res ResPutObject
(non-blocking): Can we don't introduce this variable?
I suggest:
249f76cfe8
to2c2bcfc834