mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #1742] [MERGED] Changed etaglist_t from string list to new structure etagpairs list #2150
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2150
Loading…
Add table
Add a link
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?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1742
Author: @ggtakec
Created: 8/15/2021
Status: ✅ Merged
Merged: 8/16/2021
Merged by: @gaul
Base:
master← Head:change_etaglist📝 Commits (1)
0ce4f4aChanged etaglist_t from string list to new structure etagpairs list📊 Changes
6 files changed (+77 additions, -47 deletions)
View changed files
📝
src/curl.cpp(+23 -24)📝
src/curl.h(+1 -1)📝
src/fdcache_entity.cpp(+3 -4)📝
src/fdcache_fdinfo.cpp(+8 -9)📝
src/fdcache_fdinfo.h(+2 -2)📝
src/types.h(+40 -7)📄 Description
Relevant Issue (if applicable)
n/a
Details
Changed the etaglist_t element that stores a list of
ETagvalues for multipart uploads.The etaglist_t was a list of
std::string, but I changed it to a list of newly added structureetagpair.For multipart uploads, the
ETagandpart numbermust be a pair.Currently, these are managed separately, but that has no problem.
That's because each part of the multipart is a sequential number and matches the position of the string
list etaglist_t.In this PR, we have added a new structure
etagpairwithETagandpart numberas members.And I changed
etaglist_tto a list of structsetagpair.This PR is a related modification.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.