Create a scenario for S3 overwrite #156
Labels
No labels
P0
P1
P2
P3
good first issue
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#156
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Limited number of objects. Each one is overwritten multiple times during the test.
Applicable to both versioned and non-versioned buckets.
cc @a.bogatyrev @alexvanin
It seems we already have sth similar with OBJ_NAME.
After #175 we can also set key length to a very small value which will effectively allow us to overwrite the same object, albeit with less control over parameters.
If there is a need, we could restrict alphabet too, I think current implementation is enough, though.