Message from discussion S3QL with Memset
The group you are posting to is a Usenet group
. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
From: Nikolaus Rath <Nikol...@rath.org>
Date: Fri, 16 Mar 2012 11:21:07 -0400
Local: Fri, Mar 16 2012 11:21 am
Subject: Re: [s3ql] S3QL with Memset
On 03/13/2012 02:54 PM, Nikolaus Rath wrote:
I guess I'll have to implement splitting of the metadata into different
> On 03/13/2012 02:34 PM, Stuart Wallace wrote:
>> I've had an update from Memset. It would appear that the 256 byte
>> constraint originates from the OpenStack codebase itself as can be seen
>> here (look for MAX_META_VALUE_LENGTH):
> I'm not sure what the code is. As far as I know, the OpenStack code is
> hosted on github.com/openstack/swift and the current swift version is 1.4.8.
> That said,
> seems to have the same constraint. However, I haven't heard any other
> reports of this problem and my tests with the OpenStack setups on
> RackSpace CloudFiles and bitbackup.de didn't show any problems either.
headers then. I'll see if I can find some time for that.
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
You must Sign in
before you can post messages.
You do not have the permission required to post.