From 1097c9f1d55e55e6a8f8175f5ea55e70c11b6b84 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 2 Aug 2014 23:13:41 +0000 Subject: Added a comment --- .../comment_3_d878b87a05f4fcd380e6ff309b615aab._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment b/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment new file mode 100644 index 000000000..46245e657 --- /dev/null +++ b/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.112" + subject="comment 3" + date="2014-08-02T23:13:41Z" + content=""" +There is now a workaround; S3 special remotes can be configured to use [[chunking]]. + +For example, to reconfigure an existing mys3 remote: `enableremote mys3 chunk=1MiB` + +I'm leaving this bug open because chunking is not the default (although the assistant does enable it by default), and because this chunking operates at a higher, and less efficient level than S3's own multipart upload API. In particular, AWS will charge a fee for each http request made for a chunk. + +Adding proper multipart support will probably require switching to a different S3 library. +"""]] -- cgit v1.2.3