cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edmond Lau <edm...@ooyala.com>
Subject Re: cassandra mangling non-ascii keys
Date Mon, 07 Dec 2009 22:56:22 GMT
This particular client was in Ruby.

On Mon, Dec 7, 2009 at 2:49 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
> (bugs in thrift, that is)
>
> On Mon, Dec 7, 2009 at 4:49 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
>> what language are your clients in?  there are definitely some bugs
>> there when communicating b/t client and server of different languages.
>> :(
>>
>> On Mon, Dec 7, 2009 at 4:43 PM, Edmond Lau <edmond@ooyala.com> wrote:
>>> I'm using non-ascii keys on Cassandra, relatively close to trunk at
>>> r880926, and my some of my keys get mangled.
>>>
>>> As a simple test case, if I insert a one-byte key anywhere between
>>> \200 and \377 (octal for 128 to 255) through the thrift interface, and
>>> then query back my data with multi get, I get a hash back that has
>>> "\357\277\275" as the key.  All those one-byte keys get mapped to the
>>> same bucket, so if I insert with the key \205, I get the data back
>>> when querying for \300.  So either a) there's a bug in thrift, b)
>>> Cassandra doesn't support non-ascii keys, or c) Cassandra is mangling
>>> my key somewhere.
>>>
>>> Has anyone else run into this issue?
>>>
>>> Edmond
>>>
>>
>

Mime
View raw message