Right Multipart uploads should work

Right. Multipart uploads should work, although ListParts comes to mind as something that isn’t supported yet, but should be pretty soon.
10 Replies
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
Sid
SidOP3y ago
Ah UploadPart failed? Or could this also be a CompleteMultipartUpload? One sorta weird limitation we have right now is that all parts except the last must be the same size (S3 doesn't, FWIW). This verification only happens on CompleteMultipartUpload though. Mind giving me your account id & bucket name? I can see what exactly went wrong in our logs then (account IDs and bucket names are not sensitive information, but feel free to DM me if you want)
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
Sid
SidOP3y ago
I'm sure you've looked at this compat table btW< right? https://developers.cloudflare.com/r2/data-access/s3-api/api/
S3 API compatibility · Cloudflare R2 docs
R2 implements the S3 API to allow users and their applications to migrate easily. When comparing to AWS S3, Cloudflare has removed some API …
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
Sid
SidOP3y ago
Hm so I see a bunch of multipart-related requests and I followed some of them and it looks like this happens everytime: 1. An upload is created 2. Part 1 gets uploaded successfully 3. Upload gets aborted 4. Part 2 upload fails because the upload no longer exists Oh boy am I about to set up Spark on my machine? If not that, it at least looks like upload ids are getting mixed up somehow 🤔
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
Sid
SidOP3y ago
Ah right this is true. I’m curious why Spark/the SDK is trying to decode it though Hm so the JS SDK doesn’t, why is this special 🤔 And I thought Etags were supposed to be opaque strings
Unknown User
Unknown User3y ago
Message Not Public
Sign In & Join Server To View
Sid
SidOP3y ago
Whoa nice! To be fair this was all you haha Yeah I’ll check although I don’t think we’d ever be able to match S3’s Etags, we’ve got reasons to deviate unfortunately I’m still not sure why a client would decode them, but I’ll investigate!

Did you find this page helpful?