![]() ![]() Resumable uploads are a great tool if you want to upload a single object in a single stream, in order, and you want the ability to resume if the connection is lost. Indeed, this is exactly what the gsutil command-line utility does when uploading in parallel. The best way to get those same benefits with GCS would be to upload the parts as separate objects and then using Compose to combine them into a final object. The main benefits to multipart upload are allowing multiple streams to upload in parallel from one or more machines and allowing a partial upload failure not to ruin the whole upload. Google Cloud Storage does not currently support multipart upload. ![]() Update: below answer is no longer correct. What is the best option to use? Some services already use CreateMultiPart, UploadPart, CompletePart and I need to write "adapter" for this services in order to make them compatible with google cloud storage. And there is resumable upload, that seems to allow upload files in chunks, but without complete multipart. So I see that google has closest method Compose, where I just upload different objects and then send request to combine them, or I can use uploadType=multipart, but this seems to be completely different from s3 multipart. As far as I understood google doesn't support s3 multipart, got info from here Google Cloud Storage support of S3 multipart upload. ![]() Now we are migrating to google cloud storage and we have a problem with multipart. Okay, I have a working apps that use amazon s3 multipart, they use CreateMultipart, UploadPart and CompleteMultiPart. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |