On Dec 23 2015, Nikolaus Rath <[email protected]> wrote:
> So in principle it's probably possible to do an in-place
> conversion. Such a tool would need to read the first kB or so of each
> object to get the metadata, and then write it back as "actual"
> metadata. That leaves the complication that the actual data is still
> contained at an offset in the storage object, but luckily S3QL already
> has a mechanism to handle this to support file system upgrades (there is
> a 'payload_offset' metadata entry just for this). Doing all this will
> require a bit of programming though (i.e., I would charge for doing
> it).
Thinking about it, you will also need to do some renaming. The local
backend distributes its files into subdirectories (so that an
accidential 'ls' in the data directory doesn't take ages to
complete). For S3, that's not a concern so all the storage objects live
in the same, flat namespace.
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.
