feature/lifecycle_convert_date #516
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 project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#516
Loading…
Reference in a new issue
No description provided.
Delete branch "mbiryukova/frostfs-s3-gw:feature/lifecycle_convert_date"
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?
097c0b6e36
toff57dbb1dc
@ -236,0 +312,4 @@
for {
n, err := reader.Read(buf)
if n > 0 {
println(string(buf[:n]))
Delete this line
@ -236,0 +312,4 @@
for {
n, err := reader.Read(buf)
if n > 0 {
println(string(buf[:n]))
Debug?
@ -236,0 +310,4 @@
buf := make([]byte, 64*1024)
for {
n, err := reader.Read(buf)
Why don't we use
io.Copy
orio.CopyBuffer
?@ -32,1 +30,3 @@
ExpiredObjectDeleteMarker *bool `xml:"ExpiredObjectDeleteMarker,omitempty"`
Date string `xml:"Date,omitempty"`
Days *int `xml:"Days,omitempty"`
Epoch *uint64 `xml:"Epoch,omitempty"`
Should we add the similar field (
Epochs
) toAbortIncompleteMultipartUpload
andNonCurrentVersionExpiration
I’m not sure if this is necessary, current date is not involved in days conversion
Probably it's better use duration not in days but in epochs (abort multipart not after 2 days but after N epochs after initiation)
Otherwise, it seems we will have some inconsistency. For example it we tick some epochs (e.g. in tests) we will expire objects that have specific expiration date. But we won't expire object if they have
Days
expiration@alexvanin
@ -234,2 +269,4 @@
return nil
}
func timeToEpoch(ni *netmap.NetworkInfo, t time.Time) (uint64, error) {
Consider reusing this
ff57dbb1dc
toa6372f252f