only do a multipart s3 copy when above the regular copy limit#41914
only do a multipart s3 copy when above the regular copy limit#41914juliusknorr merged 2 commits intomasterfrom
Conversation
|
/backport to stable28 |
|
/backport to stable27 |
juliusknorr
left a comment
There was a problem hiding this comment.
Seems good, do you know what s3 providers/solutions enforce such a limit?
It might need a different interface, I'm not sure if all providers that support multipart upload also support multipart copy |
No, but there are at least 2 different cases where the multipart copy is failing
I'm not aware of any good way to tell if an S3 implementation supports it |
|
For reference, I'm also affected by this issue, using Google Cloud Storage (but haven't tested this patch yet). Some built-in solution would be greatly appreciated, either a configurable limit like |
|
You should propagate |
Signed-off-by: Robin Appelman <[email protected]>
…roviders Signed-off-by: Julius Härtl <[email protected]>
34bff45 to
e405437
Compare
|
Pushed an additional commit to be able to fully turn off multipart copy for s3 providers not supporting it at all. |
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Added in nextcloud/server#41914 Signed-off-by: Josh <[email protected]>
Multipart copy seems problematic with some backends so avoid it when possible.