On 07/24/2014 02:24 PM, Andy Cress wrote: > After checking this out on both Amazon and Google, I can see that the > implementation is consistent, but not what I expected. > > A folder is created by the administrator (e.g. 'myfolder'), and the s3ql > > data for mybucket/myfolder goes into blocks in the bucket root which have > the following naming convention: > myfolders3ql_data_* > > (using s3ql-1.17) > > I'm curious. Why do those files go into the bucket root instead of into > myfolder?
There is no such as things as folders in Amazon S3 or Google Storage. The string "folder/file" is the name of an object, just like "folder+file" or "folderfile". The / character has no special meaning at all (see also http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingObjects.html). You can easily check that as follows: 1. Create an object folder/file1 3. Try to rename folder to folder_new - you will get an error, because there is no object named "folder". For convenience, the gsutil command and the AWS Management console allow you to pretend that '/' has any meaning, but it really has not. If you want s3ql to store its objects as myfolders/s3ql_data_*, you need to use myfolder/ as a prefix, not myfolder. 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.
