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
Thanks for your thoughts. That is my impression about empty directories or the
existence of directories at all in S3 too. I was trying to replicate a
hierarchy exactly out of habit. I don't think it's ultimately a requirement for
my needs.
Mike
On Mar 12, 2014, at 2:26 PM, j.merr...@enlyton.co
My impression is that there is no such thing as an "empty directory" on S3.
There really aren't hierarchical folders/directories -- it is a flat namespace.
Using / as a delimiter gives the illusion of a hierarchy, because you can have
bucket.s3.com/one/two/file.x
bucket.s3.com/one/two/file.y
bu
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
