summaryrefslogtreecommitdiff
path: root/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment
blob: 46245e657cc83e3b8a1e082e0973539af5de4d73 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
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.
"""]]