On Jul 24 2015, Chris Croome <[email protected]> wrote:
> Hi Nikolaus
>
> On Thu 23-Jul-2015 at 04:40:18AM -0700, Nikolaus Rath wrote:
>> 
>> Look for" dumb-copy" in the S3QL documentation. But note that this
>> does not speak well for your storage provider. I recommend raising
>> this issue with them instead of working around it in S3QL. 
>
> Thanks for your hep with this, using "dumb-copy" does appear to be
> working OK so far.
>
> I'm unsure exactly what to raise with this storage provider -- is the
> problem that "dumb-copy" works around documented somewhere?

Is the S3QL documentation unclear?

,----
| dumb-copy
| 
|     If this option is specified, S3QL assumes that a COPY request to
|     the storage server has succeeded as soon as the server returns a
|     200 OK status. The S3 COPY API specifies that the storage server
|     may still return an error in the request body (see the copy
|     proposal for the rationale), so this option should only be used if
|     you are certain that your storage server only returns 200 OK when
|     the copy operation has been completely and successfully carried
|     out. Using this option may be neccessary if your storage server
|     does not return a valid response body for a succesfull copy
|     operation.
`----

Your provider presumably claims to implement an S3 compatible
API. However, it's implementation of the remote copy operation differs
from Amazon's implementation. Your provider simply returns a 200 OK HTTP
status with an empty response body. Amazon's response is much more
complex (and for good reason). Relevant links (also included in the
documentation):

https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectCOPY.html
https://doc.s3.amazonaws.com/proposals/copy.html

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to