Thank you, Matt.
I appreciate this explanation from the s3cmd point of view. This improves my
growing understanding of S3 and how to best work with it.
Mike
On Mar 11, 2014, at 8:44 PM, Matt Domsch wrote:
> TL;DR: yes, it's known. No, it's not expected to get fixed soon, if ever.
> --delete
t s3 handles names that end with /
> differently than names that are the same without the /. Could you have the
> entry above and also store data in
>
> bucket.s3.com/four
>
> ? Only by experimenting could you determine that.
>
>
> J. Merrill
>
> -Original
ket.s3.com/four
? Only by experimenting could you determine that.
J. Merrill
-Original Message-
From: "WagnerOne"
Sent: Tuesday, March 11, 2014 9:32am
To: S3tools-general@lists.sourceforge.net
Subject: [S3tools-general] empty directories not syncing - known issue
Hi,
I
Hi,
I noticed empty directories on my source (not s3) side aren't making it to my
target, s3 side.
I searched the archives and saw this is a known issue. Is there a timeline for
when this may be resolved?
Also, what is the current behavior if I create the required empty directories
in s3 manu
TL;DR: yes, it's known. No, it's not expected to get fixed soon, if ever.
--delete-removed will ignore it on download too, and not delete any such
local empty directory.
S3 fundamentally is an object store, not a file system. At least that's
how it was originally presented to be, and what s3cmd
