Uh oh!
There was an error while loading. Please reload this page.
only do a multipart s3 copy when above the regular copy limit - #41914
Conversation
icewind1991
commented
Nov 29, 2023
/backport to stable28 |
icewind1991
commented
Nov 29, 2023
/backport to stable27 |
Uh oh!
There was an error while loading. Please reload this page.
juliusknorr
left a comment
There was a problem hiding this comment.
Seems good, do you know what s3 providers/solutions enforce such a limit?
juliusknorr
commented
Dec 4, 2023
It might need a different interface, I'm not sure if all providers that support multipart upload also support multipart copy |
icewind1991
commented
Dec 4, 2023
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 |
Ziyann
commented
Dec 19, 2023
You should propagate |
Signed-off-by: Robin Appelman <robin@icewind.nl>
…roviders Signed-off-by: Julius Härtl <jus@bitgrid.net>
34bff45 to
e405437Comparejuliusknorr
commented
Dec 28, 2023
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 <josh.t.richards@gmail.com>
Added in nextcloud/server#41914 Signed-off-by: Josh <josh.t.richards@gmail.com>
Added in nextcloud/server#41914 Signed-off-by: Josh <josh.t.richards@gmail.com>
Added in nextcloud/server#41914 Signed-off-by: Josh <josh.t.richards@gmail.com>
Added in nextcloud/server#41914 Signed-off-by: Josh <josh.t.richards@gmail.com>
Added in nextcloud/server#41914 Signed-off-by: Josh <josh.t.richards@gmail.com>
Added in nextcloud/server#41914 Signed-off-by: Josh <josh.t.richards@gmail.com>
Multipart copy seems problematic with some backends so avoid it when possible.